Mobile Policing Application

British Transport Police publishes IT Services work continuously — 36 notices, roughly one every 40 days. This is a stream to watch, not a cycle to wait for.

49% of British Transport Police’s awards go to a supplier it has used before.

Which is the argument for getting on the list rather than winning this one. The incumbent is rarely the last winner — it is the roster. See the retention odds by category →

Notification of forthcoming procurement 1.

Introduction 1.1 British Transport Police intends to procure and implement a mobile solution that is suitable for use by 1800-2000 frontline public facing officers and which will improve our frontline operations by May 2017.

1.2 As part of this project we intend to procure an operational policing application that can deliver the functionality required by the mobile solution to achieve the necessary benefits for our frontline operations.

This will be initially provided to the 2000 officers that are part of this project and potentially up to 4000 more staff in the future.

Further details regarding BTP, the mobile solution project and potential functionality are detailed in appendix A of this document.

1.3 The supplier of the operational application will be required to assist BTP in integrating and implementing the mobile application with the BTP mobile infrastructure and back-end policing applications by May 2017, to enable the rollout of the mobile solution.

1.4 BTP intends to procure the operational policing application using RM1042 Corporate Software Solutions framework, Lot 7.

1.5 If suppliers believe, having reviewed the requirements in Appendix A, that they have a suitable application, they may wish to contact suppliers on RM1042 (please see: http://ccs-agreements.cabinetoffice.gov.uk/suppliers?sm_field_contract_id=%22RM1042%3A7%22) 2.

Procurement Time Table with indicative dates 2.1 The indicative timetable f...e strategy.

Functionality not central to policing operations and devices for non-public facing officers and civilian staff are not within the scope of this project, but are part of the wider BTP mobile strategy.

3.3 In doing this the project also has the objectives of: 3.3.1 Supporting intelligence led policing 3.3.2 Enabling public facing officers to work away from police stations as much as possible 3.3.3 Enabling officers to access and use information on patrol in ways not currently possible 3.3.4 Enabling the transformation to new ways of working 3.3.5 Building on capabilities and efficiencies being delivered by the new integrated systems 4.

Capability requirements of Operational Application 4.1 Full details of the user requirements for the operational application will be provided in the ITT.

The following paragraphs provide a very high level summary.

4.2 To enable the delivery of the capability required, the operational application must interoperate with BTP's main policing and other systems for specific functionality, namely: 4.2.1 Control Works for command and control / CAD functionality; 4.2.2 Niche for Crime, Intelligence, Custody and Case file searching and management; 4.2.3 PNC for criminal record searching and retrieval 4.2.4 QAS for search of addresses and current residents 4.3 In addition the Operational Application may also be required to provide an Electronic Pocket Note book and other functionality which will be documented in the ITT.

Free to start. Named contacts come from published notices; the strategy is generated from the buyer’s news, accounts and people.

Five included while we’re in beta, and the agent asks before it spends on any paid step.