Agenda item

A report of the Chief Operating Officer.

The Committee received a report of the Chief Operating Officer, which summarised Priority 1 and Priority 2 incidents in March 2022, and the following points were discussed:

• A glossary of terms would be introduced for future reports.
• P1 and P2 incidents were both serious incidents: in every instance, a major incident process which followed standard good practice in the I.T. industry was followed.
• There was a query as to what resolution mechanisms were in place to deal with external dependencies which resulted in failure of service delivery.  Officers, in response, advised contracts were in place via Service Level Agreements (SLAs) and any breach of delivery was escalated through these contract mechanisms. It was agreed that the areas where action had been taken as a result of this process would be brought to the next meeting for discussion.
• There was ongoing mapping of all call systems, software products and contracts, with this work being undertaken in conjunction with the production of a joint SLA with the Shared Service to ensure that all products were covered by the Shared Service and the Agilisys contract, which was welcomed by members.
• Members heard that many of the P1s and P2s in the police were as a result of external legacy technology within policing as a whole. One key aim was for national policing to keep improving its technology and collaborate more closely with other forces via use of cloud-based technology, which would have the benefit of removing connectivity problems.
• Members asked that these issues be reported to future meetings of Resource, Risk & Estates (Police) Committee (RREC), given that committee’s remit included risk.
• In response to a query regarding when the mapping would be complete, a timeframe of approximately three to four months was given. Members asked officers to provide a progress update to RREC at the next meeting and officers confirmed this work would be undertaken.

RESOLVED, that:

i)             the report be noted;

ii)            a glossary of terms be produced for future reports;

iii)            a report on action taken (escalation via SLA) as a result of breach of delivery be brought to the next meeting;

iv)            a progress update on risk mapping be presented at the next meeting of RREC.