Digital4Democracy is a cloud based platform for the digitalization of Public Administration reporting activities it is based on Automatic speech recognition & Digital technologies enabling a new generation of verbalization services. More than 500 Public Administration are using the platform worldwide
- Real-time or batch Automatic Speech Recognition
- Archiving indexing and search of audio/video files synchronised with text
- Additional functionalities such as clipping and alerting
- Audio & Video Streaming
- Automatic video indexing word by word
- Realtime reporting with automatic speech recognition
- Audio video storage with indexing
- Multimedia pdf: a pdf with synchronised audio and text
- simplify and automate the reporting workflow in Public Sector
- Time saving, Increased productivity, increased empoyees satisfaction, cost reduction
- Customizable reporting process for any Public Administration
- Supporting different language models, Acoustic Models, accents
- Reduce the time to deliver for verbalization of the meetings
- Workforce automation and optimization of the resources
- Automatic Speech Recognition to reduce time and improve accuracy
- Archiving and indexing solution for better access to content
- Accessibility and Transparency
- Enabling the digital transformation
£0.0015 to £2 per unit per minute
- Education pricing available
+39 348 1302376
|Service constraints||No major constraints|
|System requirements||Workstations must be MS Windows based with MS Word|
|Email or online ticketing support||Email or online ticketing|
|Support response times||SLA can vary from real time to deferred support if Real-time 24x7 extra cost could be applied, no additional cost for working days office hours|
|User can manage status and priority of support tickets||No|
|Phone support availability||9 to 5 (UK time), Monday to Friday|
|Web chat support||No|
|Onsite support||Yes, at extra cost|
The SLA is based on priorities and time to respond for incident and requests, with escalation plans for incident.
Rather than give standard SLA that eventually won’t meet the customers' requirement we prefer that our support teams, local and remote, will define with the customer the priorities and the time to respond to incident and request.
When a ticket is raised with our helpdesk, a priority is assigned according to the urgency and impact of the support case.
Urgency: The urgency level is determined depending on how much functionality is
High Total/severe loss of business functionality, complete section/department affected, potential major clinical risk.
Medium Partial loss of business functionality.
Low Minor issue that does not impact business functionality.
Impact: The impact level is determined depending on the number of customers
High Whole organisation, trust, site or multiple sites; single large/multiple business units impacted.
Medium Group of users or one site affected.
Low One user affected.
The combination of impact and urgency will determine the priority.
In general, once a priority has been assigned to a case a target response, update frequency and resolution will be set to ensure we provide the best service possible.
|Support available to third parties||Yes|
Onboarding and offboarding
|Getting started||We provide on-site and/or remote training online. We provide a full set of documentation, we are available for onsite consulting prior the acquisition|
|End-of-contract data extraction||If on-premises all the data are already with the customers, if on the cloud and we provide archiving we will define the most suitable method to return the data to the customer|
|End-of-contract process||There is a license terms expiration and all the access to the platform will be deactivated unless differently agreed with the customer|
Using the service
|Web browser interface||Yes|
|Using the web interface||
The web interface is related to the usage of the Digital4Democracy platform.
All the ASR/reporting activities can be monitored through a Web interface and the assigned user can modify the status of the assignment of each tasks.
Also the activities related to interaction with the Digital4Democracy platform are alle Web based.
Security levels and users assignments can give specific rights of intervention on the platform.
|Web interface accessibility standard||None or don’t know|
|How the web interface is accessible||TT|
|Web interface accessibility testing||Tt|
|What users can and can't do using the API||We provide Web Socket API's or Restful API's to exchange data between the customer platform and the Digital4Democracy Platform|
|API automation tools||Other|
|API documentation formats||Other|
|Command line interface||No|
|Independence of resources||Every users have own environment which it can work.|
|Infrastructure or application metrics||Yes|
|Supplier type||Reseller providing extra features and support|
|Organisation whose services are being resold||Cedat85 Srl|
|Staff security clearance||Staff screening not performed|
|Government security clearance||None|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||European Economic Area (EEA)|
|User control over data storage and processing locations||No|
|Datacentre security standards||Supplier-defined controls|
|Penetration testing frequency||At least every 6 months|
|Penetration testing approach||In-house|
|Protecting data at rest||Physical access control, complying with another standard|
|Data sanitisation process||Yes|
|Data sanitisation type||Explicit overwriting of storage before reallocation|
|Equipment disposal approach||Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001|
Backup and recovery
|Backup and recovery||Yes|
|What’s backed up||
We've a script that at the end of operations provide a logs.
In case the backup process failed it sends a notification.
|Datacentre setup||Single datacentre|
|Scheduling backups||Users contact the support team to schedule backups|
|Backup recovery||Users contact the support team|
|Data protection between buyer and supplier networks||
|Data protection within supplier network||TLS (version 1.2 or above)|
Availability and resilience
- Power e Cooling Datacenter (PDC) 99.8%
- Datacenter e Rete Backbone (SDC) 99.5%
- Accesso a Internet (BI) 99%
|Approach to resilience||It's available on request|
|Outage reporting||Through email alerts|
Identity and authentication
|Access restrictions in management interfaces and support channels||Depends on platform, every user has own roles, so the system administrator define where it can access.|
|Access restriction testing frequency||At least once a year|
|Management access authentication||Username or password|
|Devices users manage the service through||Directly from any device which may also be used for normal business (for example web browsing or viewing external email)|
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||Between 1 month and 6 months|
Standards and certifications
|ISO/IEC 27001 certification||Yes|
|Who accredited the ISO/IEC 27001||IMQ|
|ISO/IEC 27001 accreditation date||19/04/2019|
|What the ISO/IEC 27001 doesn’t cover||The certification covers the full process managed by Digital4Democracy|
|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||We've just receive a issue and through a platform manage that issue with different level priority.|
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||Actually not defined|
|Vulnerability management type||Supplier-defined controls|
|Vulnerability management approach||We've a unique platform that collect every log ( not all) and define which action to do. Afterwards we classify the threat and create a rules for mitigating that one.|
|Protective monitoring type||Supplier-defined controls|
|Protective monitoring approach||We've a monitoring system that sends a several alert on services or hosts or other stuff. Afterwards fix the problem, with different priority/SLA.|
|Incident management type||Undisclosed|
|Incident management approach||The Users create a issue on a platform and a first level support defines the priority of incident and after send a email or calls a specific Business Unit.|
|Approach to secure software development best practice||Conforms to a recognised standard, but self-assessed|
Separation between users
|Virtualisation technology used to keep applications and users sharing the same infrastructure apart||Yes|
|Who implements virtualisation||Supplier|
|Virtualisation technologies used||VMware|
|How shared infrastructure is kept separate||We've a lot enviroments separated to software tier that sharing a unique infrastructure|
|Price||£0.0015 to £2 per unit per minute|
|Discount for educational organisations||Yes|
|Free trial available||No|