Official UK procurement notice
Fire Command and Control - CFRS
Authority: Cornwall Council (Local council)
What is being bought
Published requirement descriptionIntroduction
Cornwall Fire and Rescue Service (CFRS) is seeking information from suppliers capable of providing a modern Fire Control Command and Control solution to support emergency call handling, mobilisation, incident support, resilience, interoperability, and assurance.
This Request for Information (RFI) is intended to inform requirements definition, procurement approach, business case development, and market understanding. It is not a formal tender and does not constitute a commitment by CFRS or Cornwall Council to commence any procurement process or to award any contract.
Suppliers are invited to provide information on product capability, implementation approach, operating model, support arrangements, indicative timescales, and indicative costs.
Background and Strategic Context
CFRS has a statutory duty to provide effective arrangements for receiving calls for assistance and mobilising resources to fires, road traffic collisions, rescues, flooding, and other emergencies.
The current Command and Control environment is increasingly constrained, less resilient, and not technically fit for future needs. The Service is therefore preparing to procure and implement a replacement Fire Control Command and Control solution.
The replacement programme supports delivery of the Community Risk Management Plan, Fire Control Functional Delivery Plan, Service Delivery Strategy, and wider assurance, performance, and resilience requirements.
The principal drivers for change include legacy and end-of-life technology, performance and resilience concerns, the need for improved usability and reporting, the need for stronger cyber resilience, and the requirement to align with national standards and modern interoperability expectations.
Cornwall Fire and Rescue Service operate from 31 stations with a high proportion (2/3) being solely Retained crewed. Cornwall Fire and Rescues’ control room also manages this function for the Isles of Scilly Fire and Rescue Service (5 remote island stations) and any solution will include provision of the Command and Control requirements for the Isles of Scilly as well.
Cornwall is surrounded by water with only one other adjoining Fire and Rescue boundary with the Devon and Somerset Fire and Rescue Service. Service Headquarters is located at Tolvaddon, Cornwall. The current system is installed in a server room on site but the server benefits from the wider support, resource and technical capacity of Cornwall Council as its umbrella organisation.
Cornwall’s unique location and geography can present challenges for on site support so there is an expectation that the new solution will have a cloud element to it. Suppliers should therefore explain how their proposed solution aligns with Cornwall Council’s wider cloud direction, including how the design reduces dependency on local infrastructure, supports remote maintenance and management, and maintains operational resilience for a mission-critical control environment.
Current Environment
The current environment includes a legacy computer-aided dispatch / command and control platform, associated communications and interoperability components, linked telephony and mobilising arrangements, and a number of dependent interfaces and support arrangements.
The current environment contains technical and operational complexity resulting from legacy infrastructure, multiple support boundaries, and a mixture of supplier, local service, and council IT dependencies.
On site there are 8 control room operator positions, plus a technical service position, all running a Windows Operating System. There is also a server room on site with 2 physical Multitone CCP’s. Command and Control server applications currently sit on virtual servers, hosted on a Nutanix virtualized environment on site. Network infrastructure is provided by Cornwall Council.
MAIT (Multi Agency Incident Transfer) is currently provisioned via a web link to MAITweb, but an indication of embedded functionality would be helpful.
Short-term maintenance and technical refresh activity is being undertaken to preserve service continuity while full re-procurement is progressed.
Scope of Information Requested
CFRS is seeking information relating to the provision of a resilient, modern, scalable Fire Control Command and Control solution.
This may include software, platform, managed service, hosted service, implementation services, support, maintenance, resilience arrangements, disaster recovery and associated integration capability.
CFRS is interested in understanding both direct system provision and broader managed or hosted service models where relevant.
Desired Outcomes
- Improved operational resilience and continuity of the statutory Fire Control function. This should include the ability to establish a working capability off (the headquarters) site but not necessarily a second control room.
- Improved call handling and mobilisation performance
- Improved usability for operators, supervisors, and support staff
- Improved reporting, assurance, management information, and auditability
- Improved cyber resilience, security, and supportability with accreditation
- Improved interoperability with partner organisations and other emergency services
- Improved resilience for communications to third party systems including our call recording systems, availability management system, Mobile Data Terminals, vehicle navigation devices and Fire Service national incident recording systems.
- A sustainable, scalable solution that offers value for money over the contract lifecycle
- A delivery model that supports future requirements, standards, and change
- A smooth and timely transition from the existing on-premise solution to a cloud hosted service
- Minimal, if any, downtime for maintenance and technical outages.
- Management of incidents via modules or functionality such as Immediate Building Evacuation/Fire Survival Guidance/Marauding Terror Attacks/cordons. (Please specify standard and optional modules if applicable).
CPV: Software package and information systems
The lotProcurement structure
single lot · no lot value publishedLot #1PlannedRenewal
Pipeline intelligence · planning stage: how this market runs before the tender is published
How Cornwall Council buys Software package and information systems (CPV 48), and who usually turns up
Cornwall Council’s own published record, next to the published market for the same work. Frameworks and DPS are kept out: they attract a different number of bids. Whole-market view: Software package and information systems (CPV 48) →
How the contest usually goes
Winner shares use published awards; bid and price charts use contested lots.
i
How often small and medium firms win.
Share of awards where the winner’s size is known.
The counts under this question show how many awards have a known supplier size.
Small firms have won here. Neither number says whether you qualify; it describes who has been winning.
i
How often local firms win similar work.
Winners with a registered address in the delivery region, out of awards with a known address.
Here, local means registered in South West England.
A local branch does not count if the registered address is elsewhere.
Most of this buyer’s recorded winners are registered in South West England.
i
How long buyers here take to decide after bids close.
Middle value in days from the deadline to the first award notice, on competitions that published both dates.
Only decided tenders count, so slow ones still waiting are not in.
Half of these awards were announced within 39 days of the bid deadline.
i
How often work is awarded with no recorded rival.
Direct awards and tenders where every published lot count shows one bid.
Both shares are minimums: some awards have no bid count.
Thin markets produce this too; it is not proof of a tailored specification.
Direct awards or one recorded bid are common here. Check the route before spending time on a bid.
How many bids did past lots attract?
i
How many bids past lots received.
Each colour is a bid-count range. Only competed lots with a published count are included.
Past bids do not predict this tender.
1 bid12% / 13%
2–346% / 25%
4–615% / 47%
7+27% / 16%
How did awards compare with estimates?
i
Where winning prices landed against estimates.
Each colour shows awards below, close to or above the published estimate, one lot at a time.
Past prices are a guide, not a bid price.
Below estimate18% / 55%
Within ±2%64% / 35%
Above estimate18% / 10%
Assess each lot i
What past awards tell you about each lot.
See the forecast, this buyer’s earlier suppliers and firms with relevant wins.
No supplier is confirmed as a bidder.
i
What past awards tell you about each lot.
See the forecast, this buyer’s earlier suppliers and firms with relevant wins.
No supplier is confirmed as a bidder.
Open a lot for its forecast, this buyer’s previous supplier and possible competitors, from published award history, not a bid list
Lot #1Published estimate£16m
i
How many bids this lot may attract.
The forecast uses similar past competitions. The bar shows either that forecast or past bid counts; the line below says which.
Each lot shows its own forecast based on its own category; forecasts for different lots of the same notice are not comparative. The bar shows 32 past lots.
A forecast, not a list of bidders.
1 bid13%
2–325%
4–647%
7+16%
i
Where the award price may land.
The forecast uses similar awards and the buyer’s estimate. The band covers the middle half of likely prices.
No comparable awards for this lot yet.
A statistical guide from past awards, not a price to bid.
Who has supplied this buyer on similar work? i
Who has done similar work for this buyer.
Past contracts are matched by buyer, title and type of work.
A past supplier may not bid again.
i
Who has done similar work for this buyer.
Past contracts are matched by buyer, title and type of work.
A past supplier may not bid again.
No earlier contract of this buyer matches this lot on the published record.
Who could compete for this lot? i
Who could compete for this lot?
Firms with relevant past wins. On a framework, we show firms on that agreement.
None is confirmed as a bidder.
i
Who could compete for this lot?
Firms with relevant past wins. On a framework, we show firms on that agreement.
None is confirmed as a bidder.
Candidate suppliers for this notice have not been worked out yet, so this is not a verdict that nobody fits.
About this data
- Source. Official UK public procurement notices (Find a Tender), reused under the Open Government Licence v3.0. New notices arrive through the day; the figures are rebuilt nightly.
- Two views, kept apart. The authority’s own track record and the wider market for the same kind of work sit side by side and are never mixed. Where the local picture is too thin, a figure widens to a broader market and says which one it used.
- Forecasts are labelled. The price forecast and its range, possible competitors and the earlier-work matches are our estimates from past awards: not published facts, not win chances and not price advice. Official notices do not say who is bidding.
- Every figure shows what it rests on. Not every notice publishes a bid count, a value or a delivery region, so each figure carries the number of records behind it, and one built on few records is marked as such. The on a figure explains it; the counting rules are in the methodology. Spotted something wrong? Tell us.
Procedure terms & legal framework
From the official record- Legal basis
- UKPGA · 2023/54 Procurement Act 2023
- Procurement category
- Goods
- Notice status
- Planned procurement
- Procurement threshold
- Above threshold (FTS publication)
- Regulatory regime
- Standard
- Commercial structure
- Stand-alone contract (no framework)
- Competition type
- Competitive procedure
- GPA / WTO covered
- Unspecified in notice
- Recurring procurement
- Unspecified in notice
- First published
- 1 Jul 2026, 17:23 BST
- Last source update
- 1 Jul 2026, 17:23 BST
- FTS notice number
2026/S 000-061965- Latest notice
- Preliminary market engagement notice (UK2)
- Classification (CPV)
- Delivery area
- Official registry OCID
ocds-h6vhtk-06c1c7Find a Tender
How it was run
Official notice- Submission deadline
- —
Timeline
1 Jul 2026 → 1 Nov 2027 · 4 dates- Planning notice published111 days ago1 Jul 2026, 17:23 BST
- Market engagement76 days ago5 Aug 2026, 23:59 BST
Purpose of this RFI
The purpose of this RFI is to enable CFRS to understand the current supplier market and available solution models.
Responses will be used to refine requirements, shape the commercial approach, understand delivery and transition options, assess implementation risk and affordability, and inform future procurement documents.
Supplier Response Format Requirements
Suppliers wishing to participate in this market engagement exercise should contact Alex Kirk ([email protected]) and Jon Burley ([email protected]) to request a copy of the RFI document. The RFI document contains the same background and contextual information included within this engagement notice, together with the specific RFI questions that suppliers are invited to respond to. These questions are not included within this engagement notice and can only be obtained by requesting the RFI document via email. Suppliers should structure their responses in accordance with the numbering, format, and sequence of the questions set out in the RFI.
Responses should be concise, relevant, and directly address the information requested. Supporting documentation should only be provided where necessary and must be submitted as separate attachments, with clear references included within the relevant response text to indicate the associated document. Completed submissions should be emailed to Alex Kirk and Jon Burley using the email addresses provided within the RFI document. Any questions relating to the submission requirements should also be directed to Alex Kirk and Jon Burley.
Market Engagement Process and RFI Conditions
The deadline for suppliers to submit responses to the RFI questions is 5:00pm on Wednesday 5 August 2026.
The Council will host a supplier Q&A session from 11:30am to 1:00pm on Wednesday 8 August 2026. Attendance is open to all interested suppliers and the session will be held virtually via Microsoft Teams. Suppliers wishing to attend should email Alex Kirk and Jon Burley with the names of attendees. The session will provide an opportunity for suppliers to ask questions regarding both the market engagement process and the contract requirement. The Council will have a number of relevant stakeholders in attendance and will endeavour to answer questions raised during the session. However, the Council reserves the right to provide written responses following the session where it is unable, or chooses not, to answer a question verbally at the time. The session will be recorded.
The Council is also considering, and currently expects it is likely, that a series of supplier 1-to-1 engagement sessions will be held following review of the RFI responses. Only suppliers that submit a response to this RFI will be eligible to participate in any such sessions. Confirmation of whether these sessions will take place, together with details regarding dates, timings, format and arrangements, will be communicated following receipt and evaluation of the RFI responses. Should the sessions proceed, the Council anticipates that suppliers will be given an opportunity to present key aspects of their proposed solutions, which may include software demonstrations and related discussions.
Suppliers should note that this RFI is a market engagement exercise only and does not constitute a call for competition or a formal procurement process. The Council reserves the right to amend, pause, or discontinue this engagement at any time. Participation in this RFI will not confer any advantage, preference, or guarantee of invitation to any future procurement process. The Council may contact respondents following submission to seek clarification, discuss responses in greater detail, invite suppliers to presentations, or arrange follow-up workshops. Suppliers should clearly identify any information contained within their responses that they consider to be confidential or commercially sensitive.
- Today20 Oct 2026
- Tender notice expectedin 76 days4 Jan 2027, 23:59 GMT
- Contract startsin 376 days1 Nov 2027
Notice history
1 event · 1 release on Find a Tender- Preliminary market engagement notice published1 Jul 2026, 17:23 BSTUK2
Commercial outcome & contract awards
Pipeline notice- Awards (0)
- No award published
- Contracts (0)
- No contract published
- Bid statistics
- No aggregate bid statistics published
Contracting authority & participating public bodies
Official documents & specifications (1)
Official links; attachments are not copiedNotices published for this procedure
- Preliminary market engagement notice Preliminary market engagement notice on Find a Tender