Find a Tender
complete
Official procurement procedure
Command Management System (CMS) Joint Support Solution 2 (JSS2).
Command
control
communication and computer systems
+1 more
Published value
Not published
Submission deadline Not published
Lots published1
Procurement Executive Summary
AI & Search Synopsis
Generated from official OCDS record
Tenderline Synopsis: Ministry of Defence: "Command Management System (CMS) Joint Support Solution 2 (JSS2).". Published status: complete. Published value: Value not published. 1 published lot. Submission deadline not published. See the official notice for participation instructions.
| Contracting Authority | Ministry of Defence | Scope & Categories | Not published | Submission Window | complete No deadline published |
|---|---|---|---|---|---|
| Submission Gateway | Direct notice route | Legal Basis & Regime | Standard procurement | Estimated Value (exc. VAT) | Not published |
Bidder Intelligence · Authority Profile: Ministry of Defence
Market Analytics
Derived from OCDS awards & bid statistics
Published history for Ministry of Defence. These figures describe retained records, not a forecast of bids or a measure of buyer bias.
Published-to-award variance
Not availableInsufficient comparable data
Competition Density
2Bids / Report
Supplier ConcentrationNo estimate
Insufficient attributable awardsNo concentration estimate availablePayment Terms
Check noticePublished terms
Coverage: 52 active published awards; 26 bid reports (which may be per lot). Supplier values exclude multi-supplier awards, frameworks and DPS, and use GBP only. They are published award values, not payments. Published-to-award variance compares single-lot, single-award, single-supplier GBP procedures with explicitly non-framework/non-DPS status; increases remain in the average. Unpublished data stays unknown. Awarded suppliers are winners, not all bidders.
Procedure terms
Contracting AuthorityMinistry of Defence | Procedure methodNot published | Procurement categoryNot published |
Statuscomplete | Framework / DPSNot published | CompetitionNot published |
Above thresholdNot published | Legal basisNot published | Tender period startsNot published |
Clarification deadlineNot published | Electronic submissionNot published | Submission languagesNot published |
Published7 Oct 2022, 14:18 BST | Last source update7 Oct 2022, 14:18 BST | Recurring procurementNot published |
ClassificationCommand, control, communication and computer systems, Computer network services | ||
Delivery area | ||
OCIDocds-h6vhtk-0373f3 | ||
What is being bought
The Ministry of Defence (‘the Authority’), intends to place a contract amendment to the Joint Support Solution 2 (JSS2) contract (MCS/1041) with BAE Systems Limited (‘BAES’) to provide additional Shared Infrastructure (SI) nodes to host Maritime Electronic Warfare System Integrated Capability (MEWSIC) Increment 1 hardware for use on the Type 31 platform. The estimated value of this contract amendment is £10M.
What changed
From the official release history
- Status changed to complete
7 Oct 2022, 14:18 BST - Official notice release published
7 Oct 2022, 14:18 BST - Buyer information updated
7 Oct 2022, 14:18 BST
Lots and requirements (1)
Published by the contracting authority
- Lot 1 · #1Individual lot title not publishedStatus not publishedPublished valueNot publishedThe Ministry of Defence (‘the Authority’), intends to place a contract amendment to the Joint Support Solution 2 (JSS2) contract (MCS/1041) with BAE Systems Limited (‘BAES’) to provide additional Shared Infrastructure (SI) nodes to host Maritime Electronic Warfare System Integrated Capability (MEWSIC) Increment 1 hardware for use on the Type 31 platform. The estimated value of this contract amendment is £10M. In accordance with regulation 4 of The Defence and Security Public Contracts (Amendment) (EU Exit) Regulations 2019 (SI 2019/697) this procurement falls to be regulated under the provisions of the Defence and Security Public Contracts Regulations 2011 (DSPCR 2011) as amended (in particular by SI 2019/697 and SI 2020/1450). Prior publication of a contract notice in the Official Journal of the European Union is no longer appropriate. It is considered that this contract amendment can be placed using the Negotiated Procedure without Prior Publication of a Contract Notice in the UK e-notification services (as required by the relevant legislation) and is lawful in accordance with regulation 16(1)(a)(ii) of the DSPCR 2011 for Technical Reasons. This is because MEWSIC is required to be hosted upon the SI and Combat Management Systems (CMS) across the Royal Navy (RN) fleet. BAES are already on contract with the Authority for the provision of SI, and to undertake the integration of MEWSIC increment 1 hardware, with T26 SI contracted under the T26 build contract (SHIPACQ036) and QEC and T45 platforms contracted under the JSS2 contract. It is imperative to have a single and common approach covering Electronic Warfare Operators, to ensure that MEWSIC works in the same way pan-fleet (i.e., the same Form, Fit and Function plus maintenance). Having provision of SI nodes for MEWSIC and integration undertaken by a third party would not allow T31 to adopt the technical design approach of the aforementioned platforms, greatly increasing the risk of design deviation, and exposing the Authority to intolerable safety risks as well as impacting operational effectiveness, capability availability and training. Furthermore, introducing platform design differences would require different operator and maintainer guidance, thus creating issues for the Authority and RN around interoperability and safety assurance which could lead to a level of risk that is not acceptable to the Authority.Contract periodNot publishedEligibilityNot publishedOptions / renewalNot published
Timeline
- Procedure published
7 Oct 2022, 14:18 BST - Award active
Not published · Not published - Contract active
Signed 7 Oct 2022, 00:00 BST · £10,000,000
Commercial outcome and competition
Awards BAE Systems Surface Ships Ltd Not published · Not published · active |
Contracts Command Management System (CMS) Joint Support Solution 2 (JSS2) - Contract Amendment £10,000,000 · signed 7 Oct 2022, 00:00 BST · active |
Bid statisticsNo aggregate bid statistics published |
Buyer and organisations in this procedure
Ministry of Defence
Contracting authority GB-FTS-12610Documents (0)
Official links; attachments are not copied
No linked documents are published
Related procedures (0)
No related procedures published
Planning and rationale
Planning budgetNot published |
No-engagement rationaleNot published |
Procedure rationaleIn accordance with regulation 4 of The Defence and Security Public Contracts (Amendment) (EU Exit) Regulations 2019 (SI 2019/697) this procurement falls to be regulated under the provisions of the Defence and Security Public Contracts Regulations 2011 (DSPCR 2011) as amended (in particular by SI 2019/697 and SI 2020/1450). Prior publication of a contract notice in the Official Journal of the European Union is no longer appropriate. It is considered that this contract amendment can be placed using the Negotiated Procedure without Prior Publication of a Contract Notice in the UK e-notification services (as required by the relevant legislation) and is lawful in accordance with regulation 16(1)(a)(ii) of the DSPCR 2011 for Technical Reasons. This is because MEWSIC is required to be hosted upon the SI and Combat Management Systems (CMS) across the Royal Navy (RN) fleet.
BAES are already on contract with the Authority for the provision of SI, and to undertake the integration of MEWSIC increment 1 hardware, with T26 SI contracted under the T26 build contract (SHIPACQ036) and QEC and T45 platforms contracted under the JSS2 contract. It is imperative to have a single and common approach covering Electronic Warfare Operators, to ensure that MEWSIC works in the same way pan-fleet (i.e., the same Form, Fit and Function plus maintenance). Having provision of SI nodes for MEWSIC and integration undertaken by a third party would not allow T31 to adopt the technical design approach of the aforementioned platforms, greatly increasing the risk of design deviation, and exposing the Authority to intolerable safety risks as well as impacting operational effectiveness, capability availability and training. Furthermore, introducing platform design differences would require different operator and maintainer guidance, thus creating issues for the Authority and RN around interoperability and safety assurance which could lead to a level of risk that is not acceptable to the Authority. |