JIXEL AGGREGATOR is a service that allows organisations to collect information from multiple sources and channels anywhere in the world, and aggregate them in a versatile database for an easy use of the data. Sources can be either public or private; citizens are also a source when using the JIXEL-App.
- Multi-channel collector of information
- Remote access from any device with connectivity
- Optional additional channels, including social media
- Received data arranged in a optimised database
- Intuitive interface with textual and geographical data
- Compliant to CAP and MAIT standards
- Easily configured
- Dedicated App
- Receive more information in less time
- Collect information from public channels and citizens
- Easy and versatile interface
- Receive information from anyone, anywhere in the world
- Use it from your devices wherever you are
- Set your preferences and start collecting information
£3000 to £12500 per licence per year
IES Solutions LTD
|Software add-on or extension||Yes, but can also be used as a standalone service|
|What software services is the service an extension to||JIXEL, JIXEL-MANAGER, JIXEL-ALERTER, JIXEL-SHARE|
|Cloud deployment model||Private cloud|
|Email or online ticketing support||Email or online ticketing|
|Support response times||Up to a maximum of 8 hours. Monday to Friday (9 to 5 UK time)|
|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|
Customer support via helpdesk / ticketing system.
Onsite support on ad hoc basis.
Costs for onsite support will be defined on a case by case basis.
Helpdesk support is available during office hours, from 9 AM to 5 PM GMT from Monday to Friday. Support required outside of office hours must be pre-booked using the ticketing system; in this case the support service is chargeable at twice the standard hourly rate.
Classification for support issues:
1. Business Critical – The client requires urgent support to perform its duties
2. Material Fault - Interruption to normal service – The client is still able to perform the majority of the statutory duties
3. Cosmetic Fault
4. Change Request Call resolution time measures the time from when the call is recorded by the Helpdesk to the time when the call is closed. Call closure occurs when the call is resolved.
|Support available to third parties||No|
Onboarding and offboarding
For the JIXEL AGGREGATOR G-Cloud service, on-boarding process consists of:
1. Enable users access to the system
2. Configure entity's own instance of the service according to the specific needs (event typologies, other interoperable emergency authorities).
JIXEL AGGREGATOR is initially provided with a starting level of customisation required by the buyer. Then, administrative users are able to access the GUI (graphical user interface) to configure the service.
Administrative users can also access the software configuration interface (Web Service API) to import existing data (for example user accounts, events and resources types).
Off-boarding / service configuration and data extraction
We provide off-boarding configuration services for disabling each and every users’ access to the system, in the same way as we provide configuration services for users’ account insertion and other configuration capabilities. After all user access are disabled IES will completely erase the specific JIXEL AGGREGATOR instance for the entity.
Before off-boarding, the administrative users of the entity are given the ability to export (download) the latest available backup of data related to the entity's instance.
We provide users documentation through a dedicated wiki.
Onsite / online training are possible but need to be agreed beforehand on a case by case basis.
|Other documentation formats||User tutorials and services documentation on a dedicated Wiki|
|End-of-contract data extraction||When the contract ends, users will be provided with dedicated download web pages from where their data can be retrieved.|
|End-of-contract process||After the end of the contract, the JIXEL - AGGREGATOR instance of the user will be completely cleaned up and data erased. Data backup will be made available for download. No additional costs required.|
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||JIXEL - AGGREGATOR works on tablet devices without any limitation|
|Accessibility standards||None or don’t know|
|Description of accessibility||
The service provides both graphical representation (e.g. through icons on geographic map), and corresponding textual description / details, for all different information items.
The service provides an high usability degree, thanks to the following UI implementation principles:
a) All features requiring editing / insertion of information can be accessed using the keyboard
b) No time limits during users' visualisation or editing operations on web pages
c) Every feature or section of the service, and the links to other sections, easily recognised by their title or label.
d) Evidence of the textual forms that needs to be compiled by the users
|Accessibility testing||No interface testing done|
|What users can and can't do using the API||
Send (import) data into the system
Retrieve (export) data from the system
The use of the API is limited to service configuration features, and to only exporting / importing certain type of data, e.g.:
- it is possible to import geographical layers in standard formats
- it is possible to import emergency (incidents) related data using Web ATOM Feeds and Web Service / REST interfaces
- it is possible to export emergency (incidents) related data using Web ATOM Feeds
|API documentation formats||Other|
|API sandbox or test environment||No|
|Description of customisation||
JIXEL - AGGREGATOR services can be customised by using specific configuration sections. These include, for example, the possibility to add / modify / delete:
a) service users and users profiles
b) sources of information
c) event templates, types and subtypes
d) interoperability interfaces for inbound / outbound connections with other systems
e) geographic layers and related styles
|Independence of resources||Automatic system scalability of JIXEL -AGGREGATOR is ensured by the architectural and technological solutions adopted. The system is deployed in well known Cloud platform providers such as Amazon and Google Cloud. The deployment will be realised in such a way so that automatic load balancing, and vertical / horizontal scaling is ensured.|
|Service usage metrics||Yes|
|Metrics types||For admin users only, the service provides a dedicated page with information on the last registered users' activity, and last login date and time of each user|
|Reporting types||Real-time dashboards|
|Supplier type||Not a reseller|
|Staff security clearance||Staff screening not performed|
|Government security clearance||None|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||
|User control over data storage and processing locations||Yes|
|Datacentre security standards||Managed by a third party|
|Penetration testing frequency||At least once a year|
|Penetration testing approach||In-house|
|Protecting data at rest||Other|
|Other data at rest protection approach||For the Cloud infrastructure itself, JIXEL - AGGREGATOR service relies on the data at rest protection implemented by our Cloud IaaS providers, like e.g. Amazon and Google Cloud. Both comply with SSAE-16 / ISAE 3402 standards.|
|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||
Limited sets of data can be exported using dedicated software interfaces.
Large datasets belonging to the users and related to the users' activity can be made available for download at any time, upon user request.
|Data export formats||
|Other data export formats||
|Data import formats||Other|
|Other data import formats||
|Data protection between buyer and supplier networks||
|Other protection between networks||For the Cloud infrastructure itself, JIXEL - AGGREGATOR service relies on the data in transit protection mechanisms implemented by the selected Cloud IaaS providers, like e.g. Amazon and Google Cloud. For example, based on the Shared Responsibility Model of AWS, IES leverages the declared data in transit protection measures (see also the corresponding AWS G-Cloud service description). IES also uses its own data protection mechanisms, as indicated above (SSl / TLS based communication).|
|Data protection within supplier network||
|Other protection within supplier network||For the Cloud infrastructure itself, JIXEL - AGGREGATOR service relies on the data in transit protection mechanisms implemented by our Cloud IaaS providers, like e.g. Amazon and Google Cloud. For example, based on the Shared Responsibility Model of AWS, IES leverages the declared data in transit protection measures (see also the corresponding AWS G-Cloud service description). IES also uses its own data protection mechanisms, as indicated above (SSl / TLS based communication, IPsec and VPN).|
Availability and resilience
JIXEL - AGGREGATOR instances are hosted via accredited IaaS service providers such as Amazon and Google Cloud. IES Solutions or our partners manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, and individual application capabilities.
Availability is part of the resources availability and failover policy, for which we rely on IaaS providers such as Amazon, Rackspace or Google as described previously. The system is 99.99% available with no time restrictions along the whole contractual period.
No financial refunding model is foreseen. We expect full-time availability for our services, and a timely reaction and recovery of the service instance in case of unexpected failure.
|Approach to resilience||Through the IaaS it runs on, JIXEL is always provided with failover servers, networking and elastic resources. In case of very unlike and unexpected failure, backup instances of the virtualized servers are available in a matter of minutes.|
The IES technical team has put in place suitable mechanisms to timely receive notifications about outages, and even about anomalies in the resources usages (e.g. CPU and RAM usage over a certain threshold).
Notifications are received through email alerts, and the same information can be accessed any time via a dashboard.
Identity and authentication
|User authentication needed||Yes|
|Other user authentication||Username and MD5 / SHA hash password|
|Access restrictions in management interfaces and support channels||
Authorisation for the use of basically each of the provided JIXEL - AGGREGATOR features is controlled by using different users' profiles, each of them with different associated capabilities. Therefore, also access to the management (e.g. service configuration) interfaces or features is controlled through profiles and capabilities.
Access to the ticketing system provided to the customers for entering and managing tickets, is allowed only to selected users that will be designated and indicated to IES by the customer itself.
|Access restriction testing frequency||At least every 6 months|
|Management access authentication||
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||Between 6 months and 12 months|
|Access to supplier activity audit information||No audit information available|
|How long system logs are stored for||Between 1 month and 6 months|
Standards and certifications
|ISO/IEC 27001 certification||No|
|ISO 28000:2007 certification||No|
|CSA STAR certification||No|
|Other security accreditations||No|
|Named board-level person responsible for service security||Yes|
|Security governance accreditation||No|
|Security governance approach||
IES Solutions has not a security governance itself, which is directly accredited to a specific standard.
However, being JIXEL instances hosted via accredited IaaS service providers such as Amazon and Google Cloud, we rely on the security governance applied by the same service providers. For example, both Google Cloud and Amazon security governance approaches are certified according to the ISO 27001 standard.
|Information security policies and processes||While not conforming or being accredited to any specific governance standard, we follow internal rules and policies for what concerns the use of confidential information of both the company itself and our customers. Employees are not allowed to keep copy and disseminate such information to the external world. Such rules are highlighted in our internal company policy document. The CTO and one of the employees specifically accredited to this role, are responsible for controlling and ensuring the rules are followed.|
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||
While relying on third party IaaS service providers, we perform by ourselves the deployment and configuration of all JIXEL - AGGREGATOR service components in the provided Cloud infrastructure.
The same applies for any change which may be needed in the deployment architecture (e.g. in case a new data or service node instance is needed), that will be applied only by IES internal personnel.
This way, we ensure that no security risks are introduced, due to uncontrolled / untracked actions and changes.
|Vulnerability management type||Undisclosed|
|Vulnerability management approach||
For the Cloud infrastructure itself, JIXEL AGGREGATOR service relies on the vulnerability management processes of our Cloud IaaS providers. For example Amazon and Google Cloud comply with ISAE 3402 standard.
Google Cloud vulnerability management approach actively scans for security threats. Based on the Shared Responsibility Model of AWS, IES leverages the vulnerability management approach implemented by AWS for the "security of the cloud" (see corresponding AWS G-Cloud service description). IES also uses specific tools (including e.g. the Amazon Inspector tool) for software vulnerabilities monitoring ("security in the Cloud"). After threats are identified and patches are available, they are immediately applied.
|Protective monitoring type||Undisclosed|
|Protective monitoring approach||
For the Cloud infrastructure itself, JIXEL service relies on the protective monitoring processes of our Cloud IaaS providers. Both Amazon and Google Cloud comply with the ISAE 3402 standard and implement protective monitoring processes.
Based on the Shared Responsibility Model of AWS for example, IES leverages the protective monitoring approach implemented by AWS for the "security of the cloud" (see the AWS G-Cloud service description), e.g. for the identification of DDoS attacks. IES also uses commonly available tools for software services and data access monitoring ("security in the Cloud"). Response is put in place right after incident detection.
|Incident management type||Undisclosed|
|Incident management approach||
For the Cloud infrastructure JIXEL service relies on the incident management processes of our Cloud IaaS providers. Amazon and Google Cloud for example complies with the ISAE 3402 standard. Based on the Shared Responsibility Model of AWS for example, IES leverages the incident management approach implemented by AWS (see AWS G-Cloud service). IES also has its own Incident Management process which consists of the following main steps after incident detection:
a) ticket assigned to the technical development
b) after resolution, it is assigned to the test responsible
c) after verification that everything is again under control, ticket is closed
|Approach to secure software development best practice||Supplier-defined process|
Public sector networks
|Connection to public sector networks||No|
|Price||£3000 to £12500 per licence per year|
|Discount for educational organisations||No|
|Free trial available||Yes|
|Description of free trial||
We provide a trial / demo service whose use is available upon request and registration.
The trial version includes basic functionalities. It does not include customisation. The trial/demo option is free of charge and stays valid for 30 days from activation.
|Link to free trial||http://www.jixel.eu/web/en/inizia-ad-usare-jixel/|
|Pricing document||View uploaded document|
|Skills Framework for the Information Age rate card||View uploaded document|
|Service definition document||View uploaded document|
|Terms and conditions document||View uploaded document|