Purchase and Implementation of Enterprise Middleware for the University of Birmingham
The scope of this PQQ is limited to the provision of Middleware software, its installation, setup and ongoing support. It does not include hardware and any integration work.
UK-Birmingham: Software package and information systems
2013/S 094-160496
Contract notice
Services
Directive 2004/18/EC
Section I: Contracting authority
I.1)Name, addresses and contact point(s)
University of Birmingham
Edgbaston
Contact point(s): University of Birmingham
For the attention of: Jaina Rathod
B15 2TT Birmingham
UNITED KINGDOM
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
Education
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)Description
II.1.1)Title attributed to the contract by the contracting authority:
Purchase and Implementation of Enterprise Middleware for the University of Birmingham.
II.1.2)Type of contract and location of works, place of delivery or of performance
Services
Service category No 1: Maintenance and repair services
NUTS code UKG31
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 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 Middleware will support a more flexible and dynamic IT landscape within the University.
The scope of this PQQ is limited to the provision of Middleware software, its installation, setup and ongoing support. It does not include hardware and any integration work.
The University is now approaching the market to determine available products, functionality and costs for such an implementation. The University will consider open source (FOSS Free and Open Source Solutions) and proprietary (COTS Commercial Off the Shelf) solutions.
The University of Birmingham reserves the right to not award to any Tenderer.
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 Middleware will support a more flexible and dynamic IT landscape within the University.
The scope of this PQQ is limited to the provision of Middleware software, its installation, setup and ongoing support. It does not include hardware and any integration work.
The University is now approaching the market to determine available products, functionality and costs for such an implementation. The University will consider open source (FOSS Free and Open Source Solutions) and proprietary (COTS Commercial Off the Shelf) solutions.
The University of Birmingham reserves the right to not award to any Tenderer.
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
II.1.8)Lots
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:
n/a
III.1.2)Main financing conditions and payment arrangements and/or reference to the relevant provisions governing them:
n/a
III.1.3)Legal form to be taken by the group of economic operators to whom the contract is to be awarded:
n/a
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.
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 system 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 system will provide. (MS)
2. The system must provide the following as part of the ESB functionality: Transport, Queuing, 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 system including standards and protocols supported. (MS)
3. The system 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)
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 system 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 system will provide. (MS)
2. The system must provide the following as part of the ESB functionality: Transport, Queuing, 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 system including standards and protocols supported. (MS)
3. The system 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)
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:
FRAM168/13.
IV.3.2)Previous publication(s) concerning the same contract
no
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: 19.6.2013 – 12:00
IV.3.4)Time limit for receipt of tenders or requests to participate
19.6.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
English.
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
IV.3.3) Conditions for obtaining specifications and additional documents or descriptive document
Payable documents: yes
Price:
Terms and method of payment:
Payable documents: yes
Price:
Terms and method of payment:
VI.4)Procedures for appeal
VI.4.1)Body responsible for appeal procedures
not applicable
UNITED KINGDOM
Body responsible for mediation procedures
not applicable
UNITED KINGDOM
VI.4.2)Lodging of appeals
VI.4.3)Service from which information about the lodging of appeals may be obtained
not applicable
UNITED KINGDOM
VI.5)Date of dispatch of this notice:14.5.2013