Updated and historical fleet markings

Freedom of information request reference no: 01.FOI.23.028982

I note you seek access to the following information:

Would you please give me an up to date copy of the Excel file you disclosed in your response to my last question regarding fleet markings

I would note that I intend to request these files on a regular (approximately monthly) basis, to understand changes in the fleet over time, and I would appreciate assistance in streamlining the process(as I imagine yourselves would - fewer foi requests are always good!).

Some general questions:
1. Would you advise if it's possible(or even planned) to add these fields to your regular publications of fleet data, which already produces a regular list with more limited fields. I'm afraid I consider a monthly tempo to be fair, given that changes to the fleet appear to happen on a continuous basis- currently your tempo is i think twice a year.
If it is easier, a "diff" or set of changes to the fleet list would be welcome, with a full list on a 6 monthly basis.

2. Would you provide some guidance on how much work is required for you to procure a snapshot of your database at a given time?

3. If I were to want to procure historical versions of this export, to understand previous changes in fleet size or type, how could that be arranged in a manner which gives you the least hassle? I can obviously file a series of requests for these files, but optimising it seems in your interest.

4. At what point was the database software package last changed(implying a difficulty for you in producing the same dataset)

Additionally, for this request I'd like to request, for latest dataset:

5. If your database has a unique I'd for each vehicle (other than the vrn) please disclose that, or a unique derivative(such as a hash) of it, which can be used to identify the vehicle over it's lifetime (for example, identifying if it has changed paint scheme, base or roof number, etc) without disclosing the vrn.

6. The software specification provided in place of a list of columns discusses stores management. While obviously much of this information would be sensitive information, please could you include any columns discussing stores which are not sensitive in themselves (please note that section 13 of the act does not includes costs related to redaction of information - If a column contains information that would be except, but it's existence itself is not exempt, please disclose the column, redacted as nesscacery).

7. The software specification also discusses incident management and service history. Presuming incident management refers to accidents and similar damage, would you be able to include all columns and data relating to this (for example, service history, or a list of incidents and accidents which have damaged the vehicle).

8. If the results of the internal review have returned in favour of additing the vrn to my previous request, please include it, if it can be accommodated by yourselves in the time period.

With apologies for the long and detailed request,

9. CLARIFIED:
With apologies, would you mind also including columns covering milage(miles traveled in total) or engine on hours, if one exists. Please merge this into the previous request, unless you really want to treat it separately.

Decision

I have today decided to disclose some of the requested information. Some data has been withheld as it is exempt from disclosure and therefore this response serves as a Refusal Notice under Section 17 of the Freedom of Information Act 2000 (the Act) by virtue of the following exemptions:

Section 31(1)(a)(b) - Law enforcement

Reason for decision

Please find attached the updated dataset, which is in response to question

1. Please note the unit names and locations data has been removed to minimise the risk to law enforcement.

In relation to questions 2, 3 and 4 the MPS do not have recorded information relevant to these questions.

The answer to questions 5 is disclosed under the section titled information disclosed.

Please note the data in relation to questions 6,7,8,9 and 10 is exempt by virtue of section 31. In relation to question 10, please note the MPS do not record engine on hours.

Section 31(1)(a)(b) - Law Enforcement - allows public authorities to withhold information if it is likely to or would prejudice ‘The prevention or detection of crime’ or ‘The apprehension or prosecution of offenders’.

Although the MPS has previously released unit names and locations for overt vehicles we now find it necessary not to release this data in conjunction with other columns on the attached spreadsheet. In relation to question 7, all stores information and incident management and service history data held on the MPS fleet management database relates to covert assets. Providing details of the covert assets within the MPS fleet used for undercover and/or confidential investigative purposes, would disclose or infer the full operational and tactical capabilities of the MPS fleet. The details of unmarked vehicles would be invaluable information to criminals, as they would be afforded the opportunity to alter their behaviour in order to evade detection and/or destroy evidence if for example, they suspect that they are being observed.

Providing details of the unit names and locations alongside fleet numbers, VRN’s, stores information, incident management service history data and mileages would have the effect of compromising law enforcement. It has been recorded that FOIA releases are monitored by criminals and terrorists and so to provide specific information concerning our fleet, could lead to a mosaic effect with law enforcement then being undermined. You may ask how. Fleet have explained that by linking multiple datasets it will reveal significant new information which would compromise the forces’ ability to protect the public. Disclosing the MPS’ capabilities would provide persons intent on disrupting their work, with information that would assist them to do so. The safety of the public is of paramount importance to policing purposes, and any increase in crime would place the public at risk of harm.

It is worth noting that information that is made available under the Freedom of Information Act 2000 is published by the MPS via the publication scheme, making it readily available to the public, and not just the individual making the request. This is significant, as even if there is a public interest that would be satisfied by the release of the requested data this must be balanced against any identified risk. I have identified that the release of the requested data would provide a better understanding of or fleet and secondly, it provides a better understanding of how public funds are spent. These are two important factors favouring disclosure. It is important to note that the regular data about our fleet is already published via the MPS Publication Scheme.

Conversely, I have found that the release of the requested data would compromise the forces’ ability to protect the public. It is vital that the MPS is able to work covertly where necessary and deploy specialist assets in an effective manner, without fear that they will be targeted or exploited by criminal networks. Accordingly, some of the data requested has not been provided.

Disclosure

Q5 - At what point was the database software package last changed (implying a difficulty for you in producing the same dataset)

25/01/2018

Q7 - The software specification provided in place of a list of columns discusses stores management. While obviously much of this information would be sensitive information, please could you include any columns discussing stores which are not sensitive in themselves (please note that section 13 of the act does not includes costs related to redaction of information - If a column contains information that would be except, but it's existence itself is not exempt, please disclose the column, redacted as nesscacery).

Overt vehicles are maintained by an outsourced provider, Babcock Critical Services (BCS). BCS do not use the MPS database and instead use their own internal systems to manage workshop stores data.