Mobile applications transforming policing processes. Integrated with Niche RMS, Connect, Athena, nationals services. Processes include Federated Searches, Contact and Contactless Biometric Identification, Pocket Notebook, Command and Control, Tasking, Stop Search, Evidence, DASH, Briefings, Intelligence, Forms. Supports offline working and operates on Android, iOS and Windows.
- Mobile processes integrated with Force record management systems
- Off-line working model
- Cross platform support
- Federated Search capability whilst mobile
- Evidential standard of data capture
- Hosted managed mobility service
- Simple user interface to complex processes
- One time mobile input, no follow-up action in policing systems
- Officers can continue working when out of network coverage
- Force can have a mixed device estate and strategy
- Information from multiple systems returned from a single input
- Evidential at source to support digital justice process
- No on premise hardware to support the solution
- Easy to use in the field and minimal training required
£14.00 per user per month
|Software add-on or extension||Yes|
|What software services is the service an extension to||The Airpoint mobile application service is an extension to national and local police forces systems.|
|Cloud deployment model||Community cloud|
The service requires PSN connectivity and the force needs to authorise connectivity from the Airpoint data centre.
Availability of the Airpoint solution is dependent on the availability of the back office systems.
Test systems must be available for Airpoint to connect to in addition to the live environments.
Maintenance and new releases will be dependent on Force system upgrade plans.
|Email or online ticketing support||Email or online ticketing|
|Support response times||
Priority 1 within 15 minutes
Priority 2 within 4 hours
Priority 3 within 12 hours
Priority 4 within 24 hours
Standard support operates 8:00 - 18:00 Monday to Friday ex Bank Holidays.
Enhanced support operates 24/7 continuous.
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||None or don’t know|
|Phone support availability||9 to 5 (UK time), Monday to Friday|
|Web chat support||No|
|Onsite support||Yes, at extra cost|
Core support provides the application and infrastructure support Monday - Friday 08:00 to 18:00. The software element of support includes updates to ensure compatibility with supported back office systems, (PNC, Niche etc), legislation changes and minor end user device operating system upgrades. Major end user device o/s upgrades may be subject to further charges.
Enhanced support provides infrastructure support 24/7 for second line support and application management. The software element is the same as Core Support. Fixes requiring code changes will be delivered on a best endeavours basis but are subject to extensive testing and the release process.
Quarterly reviews are provided by the named technical account manager.
Pricing is covered in the price document attached to the submission.
|Support available to third parties||No|
Onboarding and offboarding
At a technical level we work with the force infrastruture team to ensure integration with the required systems and agreement regarding the security of the integration model. The onboarding process includes training the Force trainers to support roll out to end users. The mobile application is expected to be sufficiently easy to use that training documentation for end users is unnecessary.
Video based training to deploy on the device is available at extra cost.
|End-of-contract data extraction||
Airpoint provides web services to allow customers to extract the data they need in the format they want it.
If the force doesn't want to use the provided web services, Airpoint have scripts to export the data to a specific file or database format.
Six months prior to the termination or expiry of the contractual agreement Airpoint and the Customer will engage in an Exit Plan. The Exit Plan will include a mandatory Termination Discovery which will define as a minimum:
• The method, format and return of Customer generated data most appropriate to meet the exit and security requirements
• Exit timetable and appropriate milestones for the return of hardware, software and other equipment
• The compliance requirements for secure destruction and sanitisation of media
• Health & Safety and Risk Assessments
• Service exit criteria.
Airpoint will agree a price for delivering the Exit Plan and will have 10 days to transfer all Customer generated data residing within the Airpoint solution. Upon reaching the termination date, Airpoint will ensure that all of the Customer data is deleted and destroyed in a secure manner.
Using the service
|Web browser interface||No|
|Application to install||Yes|
|Compatible operating systems||
|Designed for use on mobile devices||Yes|
|Differences between the mobile and desktop service||Both mobile and desktop versions of the service remain the same, allowing a consistent user experience across all platforms.|
|Accessibility standards||None or don’t know|
|Description of accessibility||The mobile application is not strictly a web application and therefore the Web accessibility standards do not apply. However, we have reviewed the standards and where applicable applied the intent of the WCAG 2 standards to the mobile application e.g. providing text alongside iconised buttons.|
|Accessibility testing||We have undertaken usability workshops with groups of operational officers and brought their feedback into the solution to make it easy to use and fit for the operational officer in the field.|
|Description of customisation||Although the application remains a standard product across all customers, customers can take particular modules to include in the application. The customer can also request colour changes and other cosmetic changes to alter to the look of the application to represent the organisation.|
|Independence of resources||Application usage is controlled via bandwidth load balancing in certain circumstances a customer may have a virtual organisation where resources will be dedicated to that customer community.|
|Service usage metrics||Yes|
There are three levels of service usage provided with the service.
Anonymous usage of features to show number of transactions for each feature e.g. to show how many person searches have been conducted.
Usage of features combined with the user data to show usage of each feature by each user. e.g. Officer Smith has made 67 PNC searches in April 2017.
The third level of metrics is to supplement the above with the details of the data actually viewed on the mobile screen. This is primarily to support professional standards investigations and to protect officers.
|Supplier type||Not a reseller|
|Staff security clearance||Other security clearance|
|Government security clearance||Up to Security Clearance (SC)|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||United Kingdom|
|User control over data storage and processing locations||No|
|Datacentre security standards||Managed by a third party|
|Penetration testing frequency||At least once a year|
|Penetration testing approach||‘IT Health Check’ performed by a CHECK service provider|
|Protecting data at rest||Physical access control, complying with CSA CCM v3.0|
|Data sanitisation process||Yes|
|Data sanitisation type||Deleted data can’t be directly accessed|
|Equipment disposal approach||Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001|
Data importing and exporting
|Data export approach||
Individual users cannot export their data.
Airpoint provides a system wide export of data for the Force.
There is very little data actually stored within the Airpoint solution except audit information and some digital evidence if the Force does not have an existing repository.
|Data export formats||
|Other data export formats||
|Data import formats||Other|
|Other data import formats||
|Data protection between buyer and supplier networks||
|Data protection within supplier network||TLS (version 1.2 or above)|
Availability and resilience
Core - 99.95%
Enhanced - 98.90%
|Approach to resilience||Available on request|
|Outage reporting||Service outages are reported on a public dashboard|
Identity and authentication
|User authentication needed||Yes|
|Access restrictions in management interfaces and support channels||Bastion server - no direct access to management interfaces, only accessible by a registered IP address|
|Access restriction testing frequency||At least every 6 months|
|Management access authentication||Dedicated link (for example VPN)|
Audit information for users
|Access to user activity audit information||Users contact the support team to get audit information|
|How long user audit data is stored for||User-defined|
|Access to supplier activity audit information||Users contact the support team to get audit information|
|How long supplier audit data is stored for||User-defined|
|How long system logs are stored for||User-defined|
Standards and certifications
|ISO/IEC 27001 certification||No|
|ISO 28000:2007 certification||No|
|CSA STAR certification||No|
|Other security certifications||No|
|Named board-level person responsible for service security||Yes|
|Security governance certified||Yes|
|Security governance standards||ISO/IEC 27001|
|Information security policies and processes||
The Security Manual describes the reporting structure for the Company, this details each person's responsibility up to and including the Board.
Services are accrediated to the appropriate classification. RMADS document sets are produced for each service detailing the security policies and processes. Each Service is policed by the Senior Information Security Manager at the Company.
|Configuration and change management standard||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Configuration and change management approach||Customer RFCs will be raised through the Service Desk and will be managed via a Change Advisory Board who will establish the service boundaries from 3 levels of functionality: • User Service Request • Minor Change Request • Major Change Request Upon approval the System Design Authority will be responsible for producing the High-Level Design and, the Low Level Design for any proposed change to a service. After which the following procedural steps will take place: • Test & Evaluation • Quality Check • Change Implementation • Back Out Plan • Request for Change Completion • Change Wash-up|
|Vulnerability management type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Vulnerability management approach||Each service goes through a stringent risk management and accreditation assessment to ensure the relevant security incident and event monitoring technology and processes meet the guidelines set by GPG 13. The platforms are tested for vulnerability threat assessment by accredited companies annually.|
|Protective monitoring type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Protective monitoring approach||A number of SIEM best practices are employed in safeguarding and monitoring information within the managed service such as o Compliance o Access control o Perimeter Defenses o Resource Integrity o Intrusion Detection o Malware Defense o Acceptable Use In the event of a security incident the task of reporting the action will be carried out by Airpoint who will liaise with the relevant parties and collate the security information in accordance with MOD policy - GPG 13: • This information will be made available when requested by the customer authority|
|Incident management type||Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402|
|Incident management approach||• The Force service desk contacts the Service Desk (SD) to log the call and is provided a reference number and applied a priority. • The SD will then perform first-line diagnostics for the Incident. If the initial diagnosis and rectification action clears the Incident, then it is closed with the agreement of the ForceSD. • If the incident is still current, it will be assigned a resolution group. • If the incident is resolved and agreed with the ForceSD then it is closed. If however the Incident cannot be resolved within the SLA, then the escalation process will begin.|
|Approach to secure software development best practice||Conforms to a recognised standard, but self-assessed|
Public sector networks
|Connection to public sector networks||Yes|
|Price||£14.00 per user per month|
|Discount for educational organisations||No|
|Free trial available||No|
|Pricing document||View uploaded document|
|Service definition document||View uploaded document|
|Terms and conditions document||View uploaded document|