✓Tender information last checkedLast checked 14 Oct 2026, 17:56.
Opportunity overview
The BBC is moving from on-premises MAMs and editing systems, per site, to a cloud hosted TAMS based editing system, known as “Jupiter Cloud.”
The existing systems include playout servers in studios and playout functions available to the Newsroom, all controlled under a single MAM.
With the move to the cloud hosted editing system the BBC is looking for options to provide the playout servers on premises to integrate with the existing infrastructure on site.
There are currently 5 sites that will be in scope for this change, across the United Kingdon. Each site has multiple studios, up to a, current, maximum of 15 on a single site.
In order to submit an interest and participate in this request for information, please follow the following link: https://eu.mu.ariba.com/uav/project/?token=beb42f2e-60f1-4d37-a7e7-8863de8592c6
Classification
CPV48820000 — Servers
Lots
Lot LOT-0001Value not stated
Documents and notices
Preliminary market engagement notice on Find a TenderOpen source ↗
Published notice details
Additional information from the published procurement release. Fields appear only when supplied by the source; check the original notice and tender documents before acting.
Buyer location · LONDON · UKI32 · W1A 1AA · United Kingdom
Delivery location · UK · United Kingdom
Notice and amendment history
2 published notice versions reviewed by ProcuraAxis.
2 VERSIONS
1
096748-2026Preliminary market engagement notice on Find a Tender ·
2
097188-2026Preliminary market engagement notice on Find a Tender ·
PROCURAAXIS ANALYSIS
ProcuraAxis Analysis
Our approved analysis of the opportunity appears below the official tender information.
ANALYSIS PREVIEW
Opportunity intelligence at a glance
BBC is conducting preliminary market engagement (a request for information), not an open tender, for options for on-premises live-production playout servers. The servers would need to integrate with existing site infrastructure as BBC moves editing to its cloud-hosted “Jupiter Cloud” TAMS system. The indicative scope covers five UK sites, each with multiple studios (up to 15 at one site).
Who this may suit
Potential fit for suppliers with on-premises broadcast playout-server offerings and evidenced compatibility with existing broadcast-site infrastructure. This is early-stage market engagement; any eventual supplier appointment, submission requirements and commercial terms are unknown.
Key points identified
Playout-server scopeOn-premises playout servers for live productionEvidence: Title: “On-Site, Live Production Playout Servers”; description: “provide the playout servers on premises”
IntegrationServers are intended to integrate with existing on-site infrastructureEvidence: “provide the playout servers on premises to integrate with the existing infrastructure on site”
Cloud-editing contextBBC is moving to a cloud-hosted TAMS-based editing system known as Jupiter CloudEvidence: “The BBC is moving from on-premises MAMs and editing systems... to a cloud hosted TAMS based editing system, known as ‘Jupiter Cloud.’”
93% approved-analysis confidence4 supplier criteria identified4 risks or unknowns
ProcuraAxis structures information found in published procurement records, checks the result for consistency and publishes only approved analysis. Confidence describes the completeness and consistency of the available source information; it is not a guarantee of eligibility or contract award.
BBC is conducting preliminary market engagement (a request for information), not an open tender, for options for on-premises live-production playout servers. The servers would need to integrate with existing site infrastructure as BBC moves editing to its cloud-hosted “Jupiter Cloud” TAMS system. The indicative scope covers five UK sites, each with multiple studios (up to 15 at one site).
Who this may suit
Potential fit for suppliers with on-premises broadcast playout-server offerings and evidenced compatibility with existing broadcast-site infrastructure. This is early-stage market engagement; any eventual supplier appointment, submission requirements and commercial terms are unknown.
Key deliverables
Options for on-premises playout servers
Integration with existing on-site infrastructure
Indicative coverage of five UK sites
SUPPLIER REQUIREMENTS
4 criteria identified
Playout-server scope
98% confidence
On-premises playout servers for live production
View supporting evidence
Title: “On-Site, Live Production Playout Servers”; description: “provide the playout servers on premises”
Integration
95% confidence
Servers are intended to integrate with existing on-site infrastructure
View supporting evidence
“provide the playout servers on premises to integrate with the existing infrastructure on site”
Cloud-editing context
96% confidence
BBC is moving to a cloud-hosted TAMS-based editing system known as Jupiter Cloud
View supporting evidence
“The BBC is moving from on-premises MAMs and editing systems... to a cloud hosted TAMS based editing system, known as ‘Jupiter Cloud.’”
Supplier eligibility requirements
99% confidence
Unknown
View supporting evidence
No eligibility, financial-standing, insurance, company-size or certification requirements are stated in the supplied notice content.
COMMERCIAL AND DELIVERY
Contract intelligence
Commercial
Contract value
99% confidence
Unknown
View supporting evidence
value_min, value_max and currency are null.
Commercial model
98% confidence
Unknown
View supporting evidence
No pricing, contract term or commercial model is stated.
Delivery
Delivery geography
94% confidence
United Kingdom; indicative scope across five sites
View supporting evidence
“There are currently 5 sites that will be in scope for this change, across the United Kingdon.” Delivery location: United Kingdom.
Studio scale
93% confidence
Multiple studios per site, up to a current maximum of 15 at a single site
View supporting evidence
“Each site has multiple studios, up to a, current, maximum of 15 on a single site.”
Delivery timetable
99% confidence
Unknown
View supporting evidence
No contract start, end or delivery dates are supplied.
PROCEDURE
How to respond
Procurement stage
99% confidence
Planning / preliminary market engagement
View supporting evidence
stage: “planning”; source_status: “planning”; notice_type: “Preliminary market engagement notice on Find a Tender”.
Engagement mechanism
98% confidence
Request for information; suppliers are directed to an Ariba link to submit interest and participate
View supporting evidence
“In order to submit an interest and participate in this request for information, please follow the following link: https://eu.mu.ariba.com/uav/project/?token=beb42f2e-60f1-4d37-a7e7-8863de8592c6”
Tender/submission deadline
99% confidence
Unknown
View supporting evidence
submission_deadline is null. The notice describes a request for information rather than a tender.
Procurement method
99% confidence
Unknown
View supporting evidence
procurement_method and procurement_method_details are null.
RISKS AND UNKNOWNS
Points requiring attention
Early-stage engagement
99% confidence
This is preliminary market engagement / an RFI, not a confirmed tender or supplier appointment. Final scope, route, timetable, supplier requirements and commercial terms are unknown.
View supporting evidence
notice_type: “Preliminary market engagement notice on Find a Tender”; “participate in this request for information”; stage: “planning”.
Status metadata ambiguity
99% confidence
The display status is “open”, while the process stage and source status are both “planning”. The supplied notice supports an open market-engagement exercise, not an open tender.
View supporting evidence
display_status: “open”; stage: “planning”; source_status: “planning”; notice_type: “Preliminary market engagement notice on Find a Tender”.
External engagement content
98% confidence
The supplied notice directs participants to an external Ariba project link. Material RFI instructions or technical detail may exist there but were not supplied.
View supporting evidence
“please follow the following link: https://eu.mu.ariba.com/uav/project/?token=beb42f2e-60f1-4d37-a7e7-8863de8592c6”
Site-level detail
97% confidence
Individual site names, technical specifications, quantities and deployment phasing are unknown.
View supporting evidence
The notice gives only an indicative count of five sites and studio maximum; no site list or technical specification is supplied.
ProcuraAxis analysis supplements, but does not replace, the original notice and tender documents. Always verify eligibility, deadlines and commercial terms with the issuing authority.
Continue in your ProcuraAxis workspaceFree account · Full approved analysis