Middleware Solution Tender

Middleware Solution Tender

The University of Birmingham is seeking to procure a middleware solution and establish a contract with a supplier to fulfil requirements moving forward.

UK-Birmingham: Software package and information systems

2013/S 039-062339

Contract notice


Directive 2004/18/EC

Section I: Contracting authority

I.1)Name, addresses and contact point(s)

University of Birmingham
For the attention of: Jaina Rathod
B15 2TT Birmingham
Telephone: +44 1214158806
E-mail: j.rathod@bham.ac.uk

Internet address(es):

General address of the contracting authority: http://www.bham.ac.uk

Address of the buyer profile: https://in-tendhost.co.uk/universityofbirmingham

Electronic access to information: https://in-tendhost.co.uk/universityofbirmingham

Electronic submission of tenders and requests to participate: https://in-tendhost.co.uk/universityofbirmingham

Further information can be obtained from: The above mentioned contact point(s)

Specifications and additional documents (including documents for competitive dialogue and a dynamic purchasing system) can be obtained from: The above mentioned contact point(s)

Tenders or requests to participate must be sent to: The above mentioned contact point(s)

I.2)Type of the contracting authority

Body governed by public law
I.3)Main activity

I.4)Contract award on behalf of other contracting authorities

The contracting authority is purchasing on behalf of other contracting authorities: no

Section II: Object of the contract

II.1.1)Title attributed to the contract by the contracting authority:

Provision of a middleware solution for the University of Birmingham.
II.1.2)Type of contract and location of works, place of delivery or of performance

Service category No 1: Maintenance and repair services
NUTS code UKG31

II.1.3)Information about a public contract, a framework agreement or a dynamic purchasing system (DPS)

The notice involves a public contract
II.1.4)Information on framework agreement
II.1.5)Short description of the contract or purchase(s)

The University of Birmingham is seeking to procure a middleware solution and establish a contract with a supplier to fulfil requirements moving forward. The University has a large, varied and mature suite of IT systems spread across many departments. Many of these have evolved over time or have been implemented to meet specific local requirements. This has resulted in a very high degree of complexity and some duplication of functionality. In addition, this means that data and services can be hidden from potential consumers due to the difficulty in finding, identifying and combining them.
The University has performed a strategy review and identified reducing complexity of the IT landscape as a primary element. The aim is to reduce current complexity, reduce the development and implementation time for new systems, simplify support, and enable greater consumption and freedom of information. The provision of middleware will support a more flexible and dynamic IT landscape within the University.
The Universitys new IT Strategy defines the basis for a less complex, more dynamic landscape to meet the current and future needs of the business by providing a simpler, more flexible, architecture. Simply put, the Universitys objective with this procurement exercise (and the following implementation, supported by the successful supplier) is to Design and implement an enterprise level Service Oriented Architecture (SOA) Middleware solution that is relevant, high quality and fit for purpose.
As a result of a comprehensive internal scoping and visioning exercise, the University has compiled a series of key principles that will be applied to realise the institutions ambitions for its middleware solution that is robust, forward thinking and achievable. These principles are outlined below.
The middleware should:
Simplify the IT Landscape,
Provide the necessary functionality to enable intercommunication between the different legacy, current and future University IT systems,
Provide the tools necessary to develop, manage and analyse the interaction of those systems,
Provide the tools to manage the IT Governance and Registry,
Provide a platform(s) that is adaptable within a changeable environment, allowing the University to be responsive to emerging trends and/or drivers,
Interface with multiple protocols and delivery mechanisms,
Be accessible and flexible to enable its use across multiple systems areas,
Be resilient and reliable to ensure continuity of business systems and processes,
Be Fit for Purpose,
Be financially sustainable, offering impact, affordability and value for money whilst being utilised widely across the University,
Be reliable, scalable and integrate seamlessly with relevant University systems whilst complying with the relevant standards.
Be secure and auditable, offering security and analysis of messaging, installation and connectivity.
Any successful supplier must be able to deliver against these principles, and be able to show evidence of previous success.
II.1.6)Common procurement vocabulary (CPV)

48000000, 72200000, 48900000, 48810000

II.1.7)Information about Government Procurement Agreement (GPA)

The contract is covered by the Government Procurement Agreement (GPA): yes

This contract is divided into lots: no
II.1.9)Information about variants

Variants will be accepted: no
II.2)Quantity or scope of the contract
II.2.1)Total quantity or scope:
II.2.2)Information about options

Options: no
II.2.3)Information about renewals

This contract is subject to renewal: no
II.3)Duration of the contract or time limit for completion

Duration in months: 60 (from the award of the contract)

Section III: Legal, economic, financial and technical information

III.1)Conditions relating to the contract
III.1.1)Deposits and guarantees required:

III.1.2)Main financing conditions and payment arrangements and/or reference to the relevant provisions governing them:

III.1.3)Legal form to be taken by the group of economic operators to whom the contract is to be awarded:

III.1.4)Other particular conditions

The performance of the contract is subject to particular conditions: no
III.2)Conditions for participation
III.2.1)Personal situation of economic operators, including requirements relating to enrolment on professional or trade registers

Information and formalities necessary for evaluating if the requirements are met: as per the PQQ and tender documentation.
III.2.2)Economic and financial ability

Information and formalities necessary for evaluating if the requirements are met: as set out in the PQQ and tender documentation.
Minimum level(s) of standards possibly required: as set out in the PQQ and tender documentation.
III.2.3)Technical capacity

Information and formalities necessary for evaluating if the requirements are met:
as set out in the PQQ and tender documentation.
Minimum level(s) of standards possibly required:
It is recommended that Suppliers review their probable response to the PQQ against the Minimum Standards set out in the Call for Competition Notice published in the Official Journal of the European Union (OJEU) and in the section below to confirm that the organisations proposed solution/s can meet the basic requirements. If your organisation is unable to demonstrate that it can meet these requirements then it is recommended that you do not proceed to complete and submit a PQQ response
1. The solution must provide the following components as a minimum Enterprise Service Bus (ESB), Governance, and Registry. Please provide details of these, and any other components, your solution will provide. (MS)
2. The solution must provide the following as part of the ESB functionality: Transport, Queueing, Orchestration, Transformation, Mediation, Routing, Choreography, Validation, Security, Governance, Audit, and Persistence, Guaranteed Delivery. Please detail how these, and any other functionality, are delivered by your solution including standards and protocols supported. (MS)
3. The solution must support installation in a virtualized server environment even if your solution does not recommend this option.
Please describe how this is supported and any standards met. (MS)
4. The supplier must provide a defined framework for the communication and delivery of patches and version upgrades with exceptions defined for high importance fixes. Please provide details including how known bugs and issues are communicated. (MS)
5. The system must be scalable vertically (by adding resources to an instance) and horizontally (by deploying multiple instances). Please explain how this is achieved. (MS)
and as set out in the PQQ and tender documentation.
III.2.4)Information about reserved contracts
III.3)Conditions specific to services contracts
III.3.1)Information about a particular profession

Execution of the service is reserved to a particular profession: no
III.3.2)Staff responsible for the execution of the service

Legal persons should indicate the names and professional qualifications of the staff responsible for the execution of the service: no

Section IV: Procedure

IV.1)Type of procedure
IV.1.1)Type of procedure

competitive dialogue
IV.1.2)Limitations on the number of operators who will be invited to tender or to participate

Objective criteria for choosing the limited number of candidates: as set out in the PQQ and tender documentation.
IV.1.3)Reduction of the number of operators during the negotiation or dialogue

Recourse to staged procedure to gradually reduce the number of solutions to be discussed or tenders to be negotiated no
IV.2)Award criteria
IV.2.1)Award criteria

The most economically advantageous tender in terms of the criteria stated in the specifications, in the invitation to tender or to negotiate or in the descriptive document
IV.2.2)Information about electronic auction

An electronic auction will be used: no
IV.3)Administrative information
IV.3.1)File reference number attributed by the contracting authority:

IV.3.2)Previous publication(s) concerning the same contract

IV.3.3)Conditions for obtaining specifications and additional documents or descriptive document

Time limit for receipt of requests for documents or for accessing documents: 25.3.2013 – 12:00
Payable documents: no
IV.3.4)Time limit for receipt of tenders or requests to participate

25.3.2013 – 12:00
IV.3.5)Date of dispatch of invitations to tender or to participate to selected candidates
IV.3.6)Language(s) in which tenders or requests to participate may be drawn up

IV.3.7)Minimum time frame during which the tenderer must maintain the tender
IV.3.8)Conditions for opening of tenders

Persons authorised to be present at the opening of tenders: no

Section VI: Complementary information

VI.1)Information about recurrence

This is a recurrent procurement: no
VI.2)Information about European Union funds

The contract is related to a project and/or programme financed by European Union funds: no
VI.3)Additional information
VI.4)Procedures for appeal
VI.4.1)Body responsible for appeal procedures

not applicable

Body responsible for mediation procedures

not applicable

VI.4.2)Lodging of appeals
VI.4.3)Service from which information about the lodging of appeals may be obtained

not applicable

VI.5)Date of dispatch of this notice:19.2.2013