Developed by Licensing professionals, Horizon offers a uniquely complete solution for Licensing operations; covering all aspects of the Licensing process. Horizon’s powerful workflows enable full management reporting tools for internal and external reporting and management requirements.
- Complete solution for the Licensing regulatory process
- Complete Cloud solution that can also be hosted locally
- Full correspondence template creation, maintenance and management
- Traffic Lights system – users view caseloads, schedules, and deadlines
- Specific User Views – manage caseloads, deadlines, and inspections
- Full performance and statutory reporting (internal and external)
- Licensing Act 2003, Gambling Act 2005, Pleasure Boats, etc.
- Taxis, Scrap Metal Dealers, Camping and Caravan Sites, etc.
- Animal Services, Charitable Collections, Street Trading, etc.
- Out of the Box solution: integrated GIS, mapping and gazetteers
- Integrated Document Management System - enterprise management and versioning
- Efficiency - all enterprise applications from one application server
- Optimised Workflows maximise productivity
- No need for multiple suppliers to provide the system
- Complete site, case and contact history across Horizon
- Instantly deploy capabilities to any device in any location
- Omni-Channel - accept applications from multiple channels
- Designed by Licensing professionals
- Unlimited Single Site Licence - simplifies funding models
£10000 to £10000 per unit per year
- Pricing document
- Skills Framework for the Information Age rate card
- Service definition document
- Terms and conditions
0844 376 4321
|Software add-on or extension||No|
|Cloud deployment model||Private cloud|
|Service constraints||There are no constraints.|
|System requirements||Compliant Internet Browsers - e.g. Internet Explorer, Chrome, etc.|
|Email or online ticketing support||Email or online ticketing|
|Support response times||If ticket is raised during the weekend, it will be dealt with immediately on the first normal working day.|
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||WCAG 2.1 AAA|
|Phone support availability||9 to 5 (UK time), Monday to Friday|
|Web chat support||No|
|Onsite support||Yes, at extra cost|
The standard support model is the same for all customers.
A technical account manager will be provided for each customer. The Cloud support engineer is available via telephone, e-mail or video call.
Annual visits to customers by the technical account manager are offered to discuss functionality, service development, offer advice and assistance in getting the most out of the software. These visits are provided as part of the standard annual licencing and maintenance agreement.
On-site training is offered to groups for up to 8, at a daily rate of £850.
Technical user forums, on-line technical documentation inventory libraries, and on-line report ticketing system for reporting issues, asking questions, and requesting service features.
|Support available to third parties||Yes|
Onboarding and offboarding
We offer on-site training, on-line videos, an online library of technical user documentation which provides users with access to everything that they need in order to use all technical elements of the software.
The on-boarding process starts with the initial uploading of your spatial data to the Spatial Data Repository database (MS SQL Server), which StatMap technical personnel will undertake on your behalf - following consultation as to which datasets you wish to upload. As part of the set-up process, we will provide you with two days of 'Knowledge Transfer' which is for the system administrator(s) in order to show them how to set-up and create mapping and spatial applications and projects.
For more details, see the Service Specification document where full details for the On-boarding process are provided, along with getting customers up and running with using and developing the services.
|End-of-contract data extraction||
Full details are provided in the Service Specification documentation.
In summary, the following steps apply:
i) Withdraw all client access to StatMap’s SaaS facility for all StatMap products.
ii) Copy and place all client data onto a full database schema file (in the form of a SQL file), incorporating spatial data in Well Known Text (WKT) and Well Known Binary (WKB) formats. That data can then be uploaded onto any sep-arate database of the client’s choice.
iii) All data will be additionally copied to ESRI Shapefiles (where the file format restrictions permit).
iv) If requested, StatMap will also supply data in the form of text files, using WKT format for representation of the geometry / geography field.
v) All data will be sent to the client on encrypted media.
Once the client is satisfied that all data has been adequately returned and that it has been safely uploaded onto alternative storage locations, the client will inform StatMap that they are in agreement to have all data relating to their organisation removed in its entirety from the hosted server – thus protecting the business interests of the client.
|End-of-contract process||The annual licencing and maintenance contract pays for the right to use the software. If the contract is not re-newed, StatMap will - in consultation with the customer - arrange to off-board all of the customer data.|
Using the service
|Web browser interface||Yes|
|Application to install||No|
|Designed for use on mobile devices||Yes|
|Differences between the mobile and desktop service||None.|
|Description of customisation||Customisation can be applied to branding, appearance, configuration of the interface, creation and configuration of data, gazetteers, provision of functionality via the creation of Roles - which you can configure to apply to as many users and / or Groups (groups into which users can be added) as you require.|
|Independence of resources||The service is offered via a single tenant hosting instance, so therefore is entirely unaffected by other customers who may be using the service.|
|Service usage metrics||Yes|
|Metrics types||The service usage metrics are available via the Administrator tools integrated into the Horizon user interface. They can be made available to as many users as the customer wishes to grant (configured via Roles groups), but normally restricted to just a few users with administrator privileges.|
|Reporting types||Real-time dashboards|
|Supplier type||Not a reseller|
|Staff security clearance||Other security clearance|
|Government security clearance||Up to Baseline Personnel Security Standard (BPSS)|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||United Kingdom|
|User control over data storage and processing locations||Yes|
|Datacentre security standards||Complies with a recognised standard (for example CSA CCM version 3.0)|
|Penetration testing frequency||At least every 6 months|
|Penetration testing approach||In-house|
|Protecting data at rest||
|Data sanitisation process||Yes|
|Data sanitisation type||Explicit overwriting of storage before reallocation|
|Equipment disposal approach||A third-party destruction service|
Data importing and exporting
|Data export approach||
There are integrated tools within the Earthlight browser client interface which enable users to import and export data in various formats, including .shp, .tab, .mid/mif, .csv, .kml.
The customer can also be provided with .sql dump files which enables the data to easily be reloaded into whatever data the customer wishes.
|Data export formats||
|Other data export formats||
|Data import formats||
|Other data import formats||
|Data protection between buyer and supplier networks||TLS (version 1.2 or above)|
|Data protection within supplier network||TLS (version 1.2 or above)|
Availability and resilience
StatMap will use commercially reasonable endeavours to make all services available 99.99% between 6am and 11pm.
StatMap will carry out planned, preventative maintenance on a regular basis. Maintenance will be performed outside of the period of Service Desk availability listed above and we will inform the customer with details of the planned maintenance and timescales for completion with a minimum of 5 working days’ notice. Unplanned maintenance will be immediately communicated to the customer along with the action to be taken.
Following the receipt of problems with the service, StatMap will assess the availability and if it falls below the Microsoft Azure guaranteed availability, StatMap will seek to refund customers on a per day basis as a proportion of the annual licencing and maintenance contract.
|Approach to resilience||We offer additional processing power, high-availability and resilience options. This al-lows deployment of multiple eVO application instances, accompanied by software load balancers and other services to ensure that the service can better withstand periods of high activity and/or the failure of one node. These are available by buying one or more units of Additional Cloud Compute Capacity, depending on the configuration you need.|
|Outage reporting||For planned system outages and downtime, the Administration tools within the Horizon case management system browser interface enables system messages to be set to communicate with any and all users to provide them with instructions via the Horizon browser client interface. This can be used to report outages and require users to save and logout of the system.|
Identity and authentication
|User authentication needed||Yes|
|User authentication||Identity federation with existing provider (for example Google Apps)|
|Access restrictions in management interfaces and support channels||Restriction and control is provided via the Administration tools integrated into the Earthlight browser client interface. These enable management interfaces to be restricted to just those granted access to via Administration tools within Earthlight.|
|Access restriction testing frequency||At least every 6 months|
|Management access authentication||
Audit information for users
|Access to user activity audit information||Users have access to real-time audit information|
|How long user audit data is stored for||User-defined|
|Access to supplier activity audit information||Users have access to real-time 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||Information Security policies are held and developed internally and the processes are enforced by the company General Manager who is responsible for corporate information security.|
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||Components tracking.|
|Vulnerability management type||Supplier-defined controls|
|Vulnerability management approach||
We operate rapid patching and update support. The software is continually monitored for risks and any potential vulnerabilities – but is rigorously tested prior to release, using best practice software development. As such we comply fully with the recommendations made by the Cabinet Office in terms of meeting best practice with regard to the PSN framework.
Patching and upgrades to eliminate identified vulnerabilities is undertaken immediately upon identification.
|Protective monitoring type||Supplier-defined controls|
|Protective monitoring approach||Monitoring processes.|
|Incident management type||Supplier-defined controls|
|Incident management approach||
Calls and issues are tracked throughout via our Support Centre Ticket System. The pre-defined process for reporting common events is for users to log all incidents via the Support Centre Ticket System. All communication is logged and transmitted to this system. Individual users and clients report through dedicated support accounts.
Three levels of reporting provided via the software: (1) Incident reports which describe a single error instance. (2) Security logs which describe users’ activities and are used by system managers to detect any security breaches. (3) Low-level logs which are kept on the server.
|Approach to secure software development best practice||Conforms to a recognised standard, but self-assessed|
Public sector networks
|Connection to public sector networks||No|
|Price||£10000 to £10000 per unit per year|
|Discount for educational organisations||No|
|Free trial available||No|