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
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)
Section II: Object of the contract
Service category No 1: Maintenance and repair services
NUTS code UKG31
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.
48000000, 72200000, 48900000, 48810000
Section III: Legal, economic, financial and technical information
Minimum level(s) of standards possibly required: As set out in the PQQ and tender documentation.
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)
Section IV: Procedure
Section VI: Complementary information
Payable documents: yes
Price:
Terms and method of payment:
not applicable
UNITED KINGDOM
Body responsible for mediation procedures
not applicable
UNITED KINGDOM
not applicable
UNITED KINGDOM
VI.5)Date of dispatch of this notice:14.5.2013