Epimorphics Ltd

Reference Data Management Platform (RDMP)

Reference data management service: manage a hierarchy of reference terms, delegating authority to different groups and version control in an open way that helps you build trust.
Used for publishing connective reference data with persistent URIs that supports key data infrastructure, internal and external services, data integration and standards activities.

Features

  • manage reference data
  • supports delegating authority to different groups to maintain the data
  • fully standards-compliant linked data based URI core
  • reference data publication and management platform
  • manage hierarchy of reference terms, code lists and vocabularies

Benefits

  • service for publication of sustainable, trusted and usable reference data
  • publish connective reference data and support key data infrastructure
  • publish persistent URIs meeting open standards and best practice
  • embed and enforce data standards within your internal data/ICT governance
  • enables programmatic and systematic validation of codes against managed lists
  • supporting data governance and standards as 5-star data

Pricing

£700 per instance per month

Service documents

Framework

G-Cloud 11

Service ID

4 6 6 3 1 6 2 8 5 9 7 8 8 3 9

Contact

Epimorphics Ltd

Martin Merry

0127 5399069

gcloud@epimorphics.com

Service scope

Software add-on or extension
No
Cloud deployment model
Public cloud
Service constraints
No specific constraints
System requirements
  • Modern web browser
  • Web access from customer site (http and https)

User support

Email or online ticketing support
Email or online ticketing
Support response times
Dependent upon specific implementation. Generally within 4 hours during support hours (08:30-17:00, Monday to Friday, excluding UK public holidays). See Service Definition documents for full details.
User can manage status and priority of support tickets
Yes
Online ticketing support accessibility
None or don’t know
Phone support
No
Web chat support
No
Onsite support
No
Support levels
Support levels are agreed with the client during the setup phase. We also provide an incident reporting service. The basic service is available during normal business hours (09.00 – 17.30 Mondays – Fridays, excluding public holidays). We provide an email address for incident reporting and will respond to any notification within 4 hours. If an incident results in loss of service we will restore the service within 1 business day; in all other cases we will use reasonable efforts to resolve the incident as quickly as possible.
Support available to third parties
Yes

Onboarding and offboarding

Getting started
We offer support in getting started with our dedicated Linked Data Publishing service under Cloud Support. We also provide training via our Linked Data Training Service.
Service documentation
Yes
Documentation formats
  • HTML
  • PDF
End-of-contract data extraction
On termination of the contract all client data will be securely deleted. During the life of the contract clients can request access to a copy of all the data stored on the system. We have also supported public sector clients in transitioning the technology to their own infrastructure.
End-of-contract process
On termination of the contract all client data will be securely deleted.

Using the service

Web browser interface
Yes
Supported browsers
  • Internet Explorer 11
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari 9+
  • Opera
Application to install
No
Designed for use on mobile devices
Yes
Differences between the mobile and desktop service
We use responsive design wherever possible
Service interface
No
API
Yes
What users can and can't do using the API
All the functionality of the service is available through the API. Users can create new code lists, upload codes and code changes to lists and delegate management of them. Full create/read/update/delete of both lists and individual codes is supported using a REST style API.
API documentation
Yes
API documentation formats
HTML
API sandbox or test environment
Yes
Customisation available
Yes
Description of customisation
Basic branding can be applied to the service. Additional customisation can be achieved via our Linked Data Publishing Service.

Scaling

Independence of resources
Each customer's instance of the service runs on dedicated and replicated hardware - typically on AWS

Analytics

Service usage metrics
No

Resellers

Supplier type
Not a reseller

Staff security

Staff security clearance
Other security clearance
Government security clearance
Up to Baseline Personnel Security Standard (BPSS)

Asset protection

Knowledge of data storage and processing locations
Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
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
Another external penetration testing organisation
Protecting data at rest
Physical access control, complying with SSAE-16 / ISAE 3402
Data sanitisation process
No
Equipment disposal approach
In-house destruction process

Data importing and exporting

Data export approach
The service is designed to export data
Data export formats
  • CSV
  • Other
Other data export formats
  • RDF
  • JSON
Data import formats
  • CSV
  • Other
Other data import formats
  • RDF
  • Other formats possible

Data-in-transit protection

Data protection between buyer and supplier networks
TLS (version 1.2 or above)
Data protection within supplier network
  • TLS (version 1.2 or above)
  • Other
Other protection within supplier network
Network operates as a Virtual Private Cloud (VPC) within Amazon Web Services infrastructure providing full subnet isolation. Access is through passwordless ssh and TLS (>1.2).

Availability and resilience

Guaranteed availability
We typically host services on AWS who provide no availability guarantees, so we do not offer an SLA on availabilty. In practice, however, we achieve more than 99% availability.
Approach to resilience
Our service is replicated and hosted on multiple servers in different availability zones.
Outage reporting
Industry standard automated monitoring (Nagios) is used to detect outages at both service level and individual servers. Performance metrics dashboards are used to identify developing situations which can be mitigated before outages occur. Outages are notified via a messaging service (typically configured for email delivery) and a real time dashboard.

Identity and authentication

User authentication needed
No
Access restrictions in management interfaces and support channels
We provide user authentication and user-level access control.
Access restriction testing frequency
At least once a year
Management access authentication
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
  • Other
Description of management access authentication
Management access for the underlying tooling is configurable to use username / password or an OAuth2 based Identity federation service. This can be configured upon setup.

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 1 month and 6 months
Access to supplier activity audit information
Users contact the support team to get audit information
How long supplier audit data is stored for
Between 1 month and 6 months
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
PCI certification
No
Other security certifications
No

Security governance

Named board-level person responsible for service security
Yes
Security governance certified
No
Security governance approach
We take security of our service seriously. All management of the service take place over encrypted channels (TLS/SSH). The service runs in a Virtual-Private -Cloud with full subnet isolation which limits the attack surface. Instances of the service have been subjected to several formal penetration tests by external third-parties and been approved. Any (minor) weaknesses discovered by testing have been mitigated. We use shared infrastructure management cookbooks to embody best-practice for server configuration. We perform regular service updates to apply security patches for underlying software. We subscribe to security-alert channels for that software and apply emergency security patches if necessary.
Information security policies and processes
Information security is the responsibility of all employees, who are expected to be aware of security best practice and to apply it in ways commensurate with the nature of our service and of the data we hold. We have a flat management structure and it is the responsibility of the company directors to ensure appropriate security best practice is applied.

We plan to move towards ISO27001 accreditation, and anticipate further formalization of our security policy and processes as this proceeds.

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
All components of the service are subject to source code management control, with full version history, using git. This includes service configuration elements, provisioning scripts and operations cookbooks as well as code artefacts. The configuration version applied to a given service deployment is managed through IT automation infrastructure (Chef server) which maintains a history of configuration versions and enables rollback. Each developer is expected to take into account relevant factors in any change including security and operational stability, and can call on peers to help assess impacts where appropriate. Our flat management structure facilitates use of peer review.
Vulnerability management type
Supplier-defined controls
Vulnerability management approach
Instances of the service have been subjected to several formal penetration tests by external third parties and been approved. When appropriate lessons learned from these tests are embodied in operational cookbooks to ensure they are applied to future systems.

We maintain a regular maintenance schedule for update of service components and have automation to simplify the update process. All services are updated at least monthly and typically more frequently. We subscribe to security alert channels for relevant software and adjust our update schedule if priority patches are needed, including performing out-of-hours emergency patching when necessary.
Protective monitoring type
Supplier-defined controls
Protective monitoring approach
Our protective monitoring processes are tailored to the nature of our service. As an open data service provider our most significant vulnerability is denial of service, including accidental denial of service from bad clients. We detect this through automated service availability monitoring, real time performance metric dashboards and server logs. Responses include blocking requestors, rate throttling, and modifying service API implementation to remove DOS vulnerabilities. Responses times are detailed under service levels.

System compromise leading to data change would be detectable through server logs recording authorization requests and update transactions. Data is redundantly stored at multiple levels enabling quick recovery.
Incident management type
Supplier-defined controls
Incident management approach
We provide extensive monitoring for our services; most incidents are detected by our own monitoring, though we provide an email mechanism for users to report incidents. Following an incident we provide an email summary to any affected customers.

Secure development

Approach to secure software development best practice
Supplier-defined process

Public sector networks

Connection to public sector networks
No

Pricing

Price
£700 per instance per month
Discount for educational organisations
No
Free trial available
No

Service documents

Return to top ↑