Flexible, enterprise-level tool to mnipulate large quantities of data according to well defined, but often very complex rules.
Can be used to cost-effectively generate synthetic test data or anonymise production data.
Can also to apply complex rules to data which is being migrated.
- Being modular, with simple components arranged in many possible combinations.
- Processing large data typically found in organisations with many customers
- Cater for complex rule-set, while remaining simple to configure
- Ideal for data migration/integration with a data repository
- Handles multiple data sources and formats
- Flexible configuration allows data formats to be adjusted
- Able to generate large (>10m records) volumes of data
- Generates realistic synthetic data
£6900 per licence per month
|Software add-on or extension||Yes, but can also be used as a standalone service|
|What software services is the service an extension to||This service can be used as an extension to the Communications Data Retention Retrieval and Disclosure service and the Event Archive service to translate data formats like ASN.1 BER, XML and JSON for ingest and retention.|
|Cloud deployment model||Hybrid cloud|
|Service constraints||Notification of planned maintenance will be provided at least 24 hours in advance and six hours notice of emergency maintenance will be provided where possible. Maintenance windows are between the hours of 17:30 and 09:00 (UK local time) on a normal business day and/or between the hours of 08:00 and 12:00 (UK local time) on a non-business day.|
|Email or online ticketing support||Email or online ticketing|
|Support response times||
Priority 1: within 30 minutes.
Priority 2 : within 1 hour
Priority 3: within 4 hours
Priority 4: within 8 hours from receipt of call
|User can manage status and priority of support tickets||No|
|Phone support availability||9 to 5 (UK time), Monday to Friday|
|Web chat support||Yes, at an extra cost|
|Web chat support availability||9 to 5 (UK time), Monday to Friday|
|Web chat support accessibility standard||None or don’t know|
|How the web chat support is accessible||The system is based on Avaya Automated Chat 2.0 (formerly Conversive). Details on accessibility can be found at: https://www.avaya.com/en/documents/vpat---avaya-automated-chat-desk-20-2013-08-19.pdf|
|Web chat accessibility testing||Testing would have been performed by Avaya the product vendor|
|Onsite support||Yes, at extra cost|
"Priority 1 Respond within 30 minutes, resolution or work-around within 24 hours
Priority 2 Respond within 1 hour. resolution or work around within 3 Working Days
Priority 3 Respond within 4 hours, resolution or work around within 10 Working Days & Permanent Solution in next release
Priority 4 Respond within 8 hours, resolution or work around within 30 Working Days & Permanent Solution in next major release"
|Support available to third parties||Yes|
Onboarding and offboarding
A typical on-boarding project involving 2 or 3 input data formats takes about 2 to 3 months and consists of:
A Discovery phase which analyses, documents and prioritises the data translation requirements. Hosting and security aspects are also discussed and agreed. This can be expected to take 2 to 3 weeks to complete, over one or two sprints. It defines an agreed, prioritised scope for the remainder of on-boarding project.
An Alpha phase delivers an Interim Operational Capability where the scope is limited to a small proportion of the data feeds and query mechanisms. This is not just a prototype – the parts that are included are fully functional. It is normally followed by a review at which the scope and priorities for the remainder of the on-boarding are agreed.
A Beta phase delivers the Final Operational Capability with the full agreed scope. This may include some re-work of the Alpha delivery as agreed at the review. The duration of the Beta phase depends on the complexity and numbers of input and output data formats, as well as the security architecture
|End-of-contract data extraction||
Users own, retain and manage batches of data generated using the Data Translation service. CGI hold no data which the user can extract when the contract ends.
Once the contract ends, users will no longer have access to the service to extract any data
|End-of-contract process||Access to the Data Translation service will be terminated and the service torn down.|
Using the service
|Web browser interface||No|
|Application to install||No|
|Designed for use on mobile devices||No|
|Accessibility standards||None or don’t know|
|Description of accessibility||N/A|
|What users can and can't do using the API||As defined, documented and agreed in the Discovery phase of the onboarding project, files can be submitted for translation and translated files can be received.|
|API documentation formats|
|API sandbox or test environment||No|
|Independence of resources||
CGI has a sizing model for its Data Transformation service which is used to calculate the compute and storage resource requirements for each installation. This is shared and agreed with each customer in the Discovery phase of every on-boarding project and reviewed again after the Alpha phase.
Similarly, there is a sizing model for support resources which is used internally to ensure there are enough support resources to service all installations.
|Service usage metrics||Yes|
|Metrics types||Service Level Agreements are in place at a contractual level. Monthly service reporting on all aspects of the service is a key item on the monthly service review agenda with your assigned Service Delivery Manager. This is built on a standard template report, with specific additions as required by the customer. This consolidates data from call resolution/response statistics from our Service Desk, to technical metrics for performance/availability from the Cloud monitoring architecture.|
|Reporting types||Reports on request|
|Supplier type||Not a reseller|
|Staff security clearance||Other security clearance|
|Government security clearance||Up to Developed Vetting (DV)|
|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||Managed by a third party|
|Penetration testing frequency||Less than once a year|
|Penetration testing approach||‘IT Health Check’ performed by a CHECK service provider|
|Protecting data at rest||
|Other data at rest protection approach||Other methods of protecting data at rest will be discussed with the hosting provider and agreed during the Discovery phase of the onboarding project.|
|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||Users own, retain and manage batches of data generated using the Data Translation service. CGI owns and hold no user data so there is no data to export.|
|Data export formats||Other|
|Other data export formats||Specific format as defined and documented in the Discovery phase|
|Data import formats||Other|
|Other data import formats||Specific formats as defined and documented in the Discovery phase|
|Data protection between buyer and supplier networks||
|Other protection between networks||The requirement for encryption or any other type of protection of data in transit will be considered and agreed in the Discovery phase of the on-boarding project.|
|Data protection within supplier network||TLS (version 1.2 or above)|
Availability and resilience
|Guaranteed availability||The service is designed to provide 95% availability. Availability will be discussed and agreed in conjunction with the hosting provider during the Discovery phase of the on-boarding project.|
|Approach to resilience||
Typically the Data Translation service is run on a VM and has no ""real time"" constraints.
Resilience will be discussed and agreed in conjunction with the hosting provider during the Discovery phase of the on-boarding project.
|Outage reporting||The system is monitored using SNMP and alerts raised at the datacentre. A comprehensive audit trail allows for more detailed forensic analysis as required. Incidents and Problems are managed by the service desk within the Support Centre.|
Identity and authentication
|User authentication needed||Yes|
|Access restrictions in management interfaces and support channels||Standard operating system facilities are used with authentication and access control as provided|
|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||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||Yes|
|Who accredited the ISO/IEC 27001||AFNOR UK Ltd (UKAS Registration No.022)|
|ISO/IEC 27001 accreditation date||19/09/2016|
|What the ISO/IEC 27001 doesn’t cover||
Nothing is NOT covered.
The following IS covered from a Technical perspective: Provision of outsourcing sevices including managed infrastructure services, contact centre services, service desk services, management of print and email, application development, maintenance and support services.
The following IS covered from a Business perspective: The provision of outsourcing, project and consultancy services, including development and delivery activities, plus the management of people, technologies and physical security.
|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||
Our security, information security and data protection management system for CGI is established through the Enterprise Security Management Framework (ESMF). The framework applies to the work we conduct for ourselves and for clients under UK contracts. All CGI UK members and contractors are expected to comply with its principles and processes.
The ESMF is comprised of:
A first level suite of security policies and security requirements that apply across the CGI enterprise.
A second level set of standards set out how these policies and requirements are met, these being detailed within the following operational categories:- Access Control- Operations- Technology- Applications- Data management- HR and Organisation- Physical"
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||
The Support Centre uses Subversion for Version Control and Trac for tracking issues. Change Requests are managed as tickets in Trac.
Change Management process is summarised below:
The client makes the request to the service desk (including when it is required by)
Service Support provides an Impact Assessment and a man-day estimate and timeline
On confirmation of acceptance, the change is planned and the release and/or patch date confirmed
|Vulnerability management type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Vulnerability management approach||All CGI and customer managed systems are kept current with vendor patches (both operational and security) with vulnerability tests performed regularly. Systems are prioritized based on criticality of known vulnerabilities. All changes are strictly controlled through CGI’s change management process.|
|Protective monitoring type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Protective monitoring approach||Please see the CGI - Security Operations Centre (SOC) - Protective Monitoring Service for full details of these processes|
|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||
CGI has a very well-defined security incident management standard and supporting process to handle all phases of a security incident. Responsibilities are clearly defined at all levels. Priorities are established to ensure the timely resolution of incidents. Records of incidents are maintained and reported to senior management. Incidents considered to be severe (high priority) are managed through CGI’s Incident Management Centre (IMC), who coordinate/escalate all required parties based on priority. Collection/preservation of evidence is carefully observed throughout the process.
Incident exercises are performed regularly to ensure the process works as expected when needed.
|Approach to secure software development best practice||Supplier-defined process|
Public sector networks
|Connection to public sector networks||Yes|
|Price||£6900 per licence per month|
|Discount for educational organisations||No|
|Free trial available||No|
|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|