DIGITAL SCIENCE UK LIMITED

Research Repository for Government, Non-Government, and Intergovernmental Organisations - Figshare

Figshare is a cloud-based, next-generation repository system. Any file format can be uploaded and published, subject to approval by client administrators. Figshare includes file previews for common formats, an open API, private collaborative spaces, automatic DOIs or handles, and reporting dashboards.

Features

• Fully managed AWS EC2 SaaS solution with multiple releases annually
• Upload, describe and publish files of any format
• In-browser previews/visualisations for common file formats
• Each metadata record describes zero, one or multiple files
• Organise records using groups hierarchy, collections or projects
• Assign administrative roles to users at organisation or group level
• Review workflow to approve submissions before they are made public
• All public items receive a DataCite DOI or other PID
• Embargo and restrict access to records
• Awards Management or local/cloud storage

Benefits

• No in-house IT support necessary after implementation
• Publish datasets, videos, maps, images, documents all in one repository
• Appeal to internal researchers and external reusers with engaging interface
• Figshare acts as a data catalogue as well as repository
• Promote groups, conferences etc through differently branded subportals
• Central or devolved administration of your repository as you prefer
• Open API and FTP for working with large/many files
• DOIs can be reserved in advanced
• Share private content as needed through Projects or sharing links
• Choose terminal file storage location/region

• Free trial available

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at rfp@digital-science.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

828318133456660

Contact

Deb Shepherd
07731475389
rfp@digital-science.com

About your service

• Service categories:

  Applications

  Content workflow and management

  • Capture
  • Document
  • Media Services

  Content services

  • Enterprise Content Management Applications
  • Content Sharing and Collaboration Applications

  Persuasive content management

  • Digital Asset Management Applications

  Enterprise portals and digital workspaces

  • Multi-Audience Portals
• Multi cloud support: No

Service scope

• Software add-on or extension: Yes, but can also be used as a standalone service
• What software services is the service an extension to: Figshare integrates with Symplectic Elements as a fully functional repository data source, enabling Figshare record creation/file upload and harvesting of metadata back into Symplectic Elements. Figshare also integrates with Dimensions, sourcing citation counts and grant record links for repository records and as a built-in viewer within Dimensions.
• Cloud deployment model: Public cloud
• Service constraints: Figshare releases and maintenance are deployed live with no scheduled downtime. The maximum file size supported is determined by the storage used (AWS is 5TB) and may be further restricted by user's browser or storage allocation. There are soft limits on the number of files per item, users per Project etc, but these can be modified for each client. If client-provided storage is used, it must have a suitable REST API. Only one storage solution can be integrated with the repository. Clients can specify regions for file storage on Figshare AWS, but not for metadata and profile information.
• System requirements:
  • Firefox 100
  • Chrome 101
  • Opera 86
  • Safari 15
  • Edge 100
  • For SSO integration must be SAML 2.0 compliant
  • Integration with local storage requires an HTTP connection

User support

• Email or online ticketing support: Yes
• Support response times: New support tickets all receive an immediate automatic email response, containing a copy of the request and a ticket number so that follow-ups can be tracked, or so that the issue can be escalated if necessary. The Figshare SLA details the response times for different severities of issues. For the most severe issues (for which no workaround exists and which has caused an immediate and material adverse business impact), the initial response time is 4 working hours.
• 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 is available throughout the subscription to the service - please see Figshare’s standard SLA for more details about our commitments. Each customer is assigned a dedicated technical account manager, who can be contacted directly, and a team of engineers - this is all managed via Asana. Administrators will be able to log in to Figshare’s support site (http://support.figshare.com/) where support tickets can be submitted, and use the Slack community to ask questions or find out more about best practice. Figshare’s support team aims to respond to all tickets within 24 hours. Support tickets can be assigned a priority level and status level. After implementation, the support platform is available for more general support, queries and feature requests. Training support will be provided during implementation and the customer is provided access to an admin user guide and user guide, API documentation, release notes, webinars and more. Furthermore, admins are provided with comprehensive release notes demonstrations which are carried out approximately every other month. Optional virtual training can also be requested and may incur a fee.
• Support available to third parties: Yes

Onboarding and offboarding

• Getting started: Once the production environment is live, administrators are provided with access to an admin user guide, API documentation, release notes, webinars, and video tutorials reviewing the interface. The admin user guide, which includes text and gifs for describing administration tasks, can be copied and amended to include your branding and specific implementation customisations. End users have comprehensive user guides (https://info.figshare.com/user-guides/) with How-to guides, information and tips and more. These resources (for both user and admin) are updated after each major development release and are therefore always up-to-date. Optional virtual training can also be requested and may incur a fee.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: All public content - files and metadata - can be extracted using open API endpoints. All private content - files and metadata - can be extracted using secure API endpoints. Individual users can also download their own files and download metadata records in various formats through the user interface. The offboarding documentation indicates options for DOI redirects and data extraction. Data extraction is the Client’s responsibility and can be completed fully by a Client using the API. Guidance on this process is available as part of included support hours up to the end-of-contract date.
• End-of-contract process: At the point of cancellation, the Figshare team will confirm end-of-contract date. On that date (or earlier date, as agreed), the Figshare services will be terminated, including: the Figshare portal(s), Figshare.com, Figshare widgets (i.e. embedded Figshare items on websites), the Figshare API. Guidance on data extraction, DOI redirects, and other tasks is available as part of included support hours up to the end-of-contract date.
• Documentation accessibility standard: None or don’t know
• How the documentation is accessible: The Figshare Support site, built on the Freshdesk customer service platform, is designed for instant self-service, enabling users to quickly find the information they need. It serves as a central resource for documentation, including onboarding and offboarding guides.; Freshdesk is committed to adhering to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standard for its products and websites. If users require information from the Figshare Support site in an alternative format, such as accessible PDF, large print, easy read, or audio recording, they should contact us at support@figshare.com.

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
  • Opera
• Application to install: No
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: Limited ability to upload files, depending on the workflows on your mobile device between browsers and stored files. Search, browse and viewing functions fully.
• Service interface: Yes
• User support accessibility: None or don’t know
• Description of service interface: The web-based service interface provides users with search, file preview, and file download options along with affordances based on a variety of widgets. Account holders have access to a private side interface that allows metadata creation and editing, file upload, profile editing, and API application and token creation. All public facing interfaces are compliant with European accessibility standard en 301 549. Figshare meets almost all WCAG 2.2 Level A requirements and is working to meet a greater number of Level A and Level AA criteria.
• Accessibility standards: None or don’t know
• Description of accessibility: Figshare has a mix of compliance levels across WCAG 2.2 Level A and AA criteria, with the fifteen criteria being ‘Supported’ and thirty criteria ‘Partially supported’. We are committed to making continued accessibility improvements across the system until we are conformant with WCAG 2.2 Level A and AA. Figshare supports:; ; Zoom of up to 200% without problems across almost all public pages; Navigation across most of the website using just a keyboard; Navigation across most of the public website using speech recognition software; Use of the majority public website using a screen reader.
• Accessibility testing: Figshare uses a combination of static analysis tools and manual testing with assistive technologies to verify accessibility claims.
• API: Yes
• What users can and can't do using the API: Figshare provides a fully-featured two-way RESTful API, documented at http://docs.figshare.com/ using Swagger. The documentation site enables rapid prototyping, as API queries can be written and the responses viewed, in the documentation site. Example code snippets are provided for multiple languages. The Figshare API is at https://api.figshare.com/v2. All communication is done through https and all data is encoded as JSON. The Figshare API provides endpoints that allow you to: - Upload files to create a new Item - Search for public and private items - List the metadata of a public item - Show details of files associated with an item - Report on whether items are embargoed confidential - Publish an Item - Reserve a DOI or handle ahead of publication - Update metadata - Change embargo settings - Create/disable a private sharing link - Create/update accounts - Add and remove admin roles - Upload a user feed - Harvest metadata through OAI-PMH. An API user group shares ideas and knowledge across our clients. See https://idn.web.ox.ac.uk/article/online-labour-index-case-study/ for an interactive visualisation for data stored in Figshare.
• API documentation: Yes
• API documentation formats: Open API (also known as Swagger)
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: During implementation, requested by the client implementation team: - Domain of repository site: either a client domain or *.figshare.com - Custom branding logo and background image. Each public subportal can have its own branding - Define links in the masthead - Define links in custom footer (to a client’s own pages) - Define group hierarchy for the repository - Define which identifier type is minted for items in each group - Configure reporting dashboard - Define a scheme of custom Categories if the default Fields of Research scheme is not wanted - Turn off the Projects and/or Collections features if not wanted. By raising a support ticket, top-level administrators can: - Add new or amend existing branding - Amend custom footer links - Modify reporting dashboard - Request custom management information report In the admin web interface, by owner of the appropriate group, or by top-level administrator: - Assign admin roles to users - Add subgroups to the hierarchy - Add descriptions text for each group - Define custom metadata fields at the organisation or group level - Define ‘Tips’ help text for each custom metadata field.

Scaling

• Independence of resources: Figshare runs in a high-availability setup using multiple AWS ELBs that forward requests to AWS EC2 instances deployed across multiple availability zones. This setup provides an easy way to scale horizontally in localised regions or globally. All information regarding item metadata, file metadata, HR feed, and user profiles are stored inside a MariaDB multi-master replication setup. Replication and restore procedures allow Figshare to scale up, adding extra nodes and load balance across them as needed. All article metadata and statistics are placed on dedicated Elasticsearch clusters, allowing us to handle an ever-growing number of concurrent search list requests.

Analytics

• Service usage metrics: Yes
• Metrics types: Public stats page provides on-screen graphs of views and downloads by date range, filterable by Group, Item type, and timeframe. Internal reporting dashboard provides various graphs, maps and tables, on usage and repository statistics and data is downloadable in CSV format. The Figshare API provides statistics endpoints. Custom reports can be requested through support requests. Figshare is Make Data Count and COUNTER compliant.
• Reporting types:
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request
• Resource tagging: No
• FOCUS resource tagging: No

Resellers

• Supplier type: Not a reseller

Staff security

• Staff security clearance: Other security clearance
• Government security clearance: 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: No
• Datacentre security standards: Complies with a recognised standard (for example CSA CCM version 4.0)
• Penetration testing frequency: At least once a year
• Penetration testing approach: Another external penetration testing organisation
• Protecting data at rest:
  • Physical access control, complying with CSA CCM v4.0
  • Physical access control, complying with SSAE-18 / ISAE 3402
  • Other
• Other data at rest protection approach: AWS uses Physical access control, complying with CSA CCM v4.0 and SSAE-18 / ISAE 3402. Outside of AWS specific physical technical controls, Figshare uses encryption for all storage devices and services used on AWS (EC2 EBS, AWS S3). Encryption keys are managed via AWS KMS.
• Data sanitisation process: Yes
• Equipment disposal approach: Complying with a recognised standard, for example CSA CCM v4.0, CAS (Sanitisation) or ISO/IEC 27001
• Data sanitisation type: Deleted data can’t be directly accessed / Cryptographic Erasure

Data importing and exporting

• Data export approach: All public content - files and metadata - can be extracted using open API endpoints. All private content - files and metadata - can be extracted using secure API endpoints. Individual users can also download their own files and download metadata records in various formats through the user interface. Metadata can also be harvested through OAI-PMH endpoints. Administrators can export metadata as CSV.
• Data export formats:
  • CSV
  • Other
• Other data export formats:
  • JSON
  • XML – Dublin Core
  • XML – DataCite
  • XML – RDF
  • XML – CERIF
  • XML – Qualified Dublin Core
  • XML – METS
  • XML – UKETD_DC (EThOS)
• Data import formats:
  • CSV
  • Other
• Other data import formats:
  • JSON (for metadata upload through the API)
  • Any file format can be uploaded to the Figshare repository

Data-in-transit protection

• Data protection between buyer and supplier networks:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
• Other protection between networks: All Figshare public endpoints are available only via HTTPS endpoints (HSTS enabled) using the ELBSecurityPolicy-TLS13-1-2-2021-06; AWS ALB security policy. Inter-cloud communications are deployed over IPSec based VPNs. ELBSecurityPolicy-TLS13-1-2-2021-06 supports TLS 1.2 and TLS 1.3
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
• Other protection within supplier network: All Figshare services are deployed inside AWS VPCs with the following technical controls implemented to protect data: - Use of private only subnets - Use of NAT Gateways for instance internet access - Use of AWS Client VPN for operational remote access - EBS encrypted volumes for all EC2 instances - S3 encrypted buckets - Environment segregation at the VPC level (dedicated VPCs for each environment) - Use of VPC Endpoints for intra VPC S3 communications - Use of dedicated subnets (NACLs) for applications and storage services - Use of TLS for inter-microservice communications (where applicable)

Availability and resilience

• Guaranteed availability: We commit to making the Platform available at least 99.9% of the time during each full calendar month, subject to the exclusions set forth below (the “Uptime Service Availability”). Periods where the Platform is not available due to the following reasons shall be excluded from the calculation of Uptime Service Availability: (i) any Force Majeure Event, which shall include any internet access or related problems beyond the demarcation point of the Storage Services; (ii) any breach of this Agreement by you or any actions or inactions of you or any third party; (iii) your equipment, software or other technology and/or third party equipment, software or other technology (other than third party equipment within our direct control); (iv) and planned maintenance carried out during the maintenance window of 05:00am to 09:00am UK time. Sufficient notice will be given for any unscheduled period during which the availability of the Platform is suspended as soon as reasonably practicable.
• Approach to resilience: The Figshare platform is deployed within AWS. To achieve a highly available and fault-tolerant setup, all Figshare services are deployed across multiple AWS availability zones. Horizontally scaling storage solutions are used across the platform: multi-node MariaDB Galera Cluster, ElasticSearch cluster, AWS S3. All public services are deployed behind AWS Application Load Balancers configured to route traffic between EC2 instances across multiple availability zones. Figshare also maintains a backup disaster recovery location as documented in the Figshare’s Disaster Recovery Plan which is available upon request. To ensure an adequate level of security the following technical controls and deployed across our infrastructure: - 24/7 automated monitoring - OS level monitoring - Application monitoring - Vulnerability management - Real-time analysis For details on AWS's resilient workload and RTO please see: https://wa.aws.amazon.com/wat.concept.resiliency.en.html
• Outage reporting: Public Dashboard and Email Alerts. Figshare provides current and historical status information at https://status.figshare.com/. This site is immediately updated whenever there is a service issue. The site includes an email alerts facility and during the implementation process, we ensure that all clients register for alerts.

Identity and authentication

• User authentication needed: No
• Access restrictions in management interfaces and support channels: Figshare integrates with the client’s SAML 2.0-compliant authentication system (e.g. Shibboleth). This must expose externally verifiable IDs to Figshare for all user accounts to ensure that they are unique. The two most common ways to create Figshare user accounts are by sending us a user feed, or by creating accounts at first login (using your authentication system). For clients without a SAML 2.0 compliant authentication system we can create accounts manually. We use a ticketing system for our support site and a project management platform to manage implementations. Relevant client staff will be able to create accounts on those systems.
• Access restriction testing frequency: At least every 6 months
• Management access authentication:
  • Identity federation with existing provider (for example Google Apps)
  • Username or password

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: At least 12 months
• Access to supplier activity audit information: Users contact the support team to get audit information
• How long supplier audit data is stored for: At least 12 months
• How long system logs are stored for: Between 1 month and 6 months

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: Yes
• Security governance standards: ISO/IEC 27001
• Information security policies and processes: Figshare is ISO27001 certified. The following policies and principles are maintained and additional information can be supplied upon request: -Information Security Policy - Access Control Policy - Secure Software Development Policy - Secure Software Engineering Principles - Change Management Policy - Password Policy - Mobile device and teleworking policy - Bring Your Own Device Policy - Physical and Environmental security policy - Stored Information Handling Procedure - Clear Desk and Clear Screen policy - Acceptable Use Policy - IT Disaster Recovery Plan - Policy on assigning and refreshing hardware equipment - Incident management procedure - Use of cryptographic controls policy - Virtual private network policy - Scope of information security management - Information transfer policy - Departmental policy on personnel training (HR) - Backup policy - Communication procedure - Risk assessment and risk treatment methodology- - Information Classification Policy - Asset Classification Policy
• Software Security Code of Practice: No

Operational security

• Configuration and change management standard: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Configuration and change management approach: The company categorises 3 change types: Standard, Normal and Emergency. All Normal and Emergency changes require explicit (pre)approval and tracking and include mandatory security control review pre and post change. Part of the ISMS, the company maintains current asset/vendor inventory, performs routine reviews for asset access controls and tracks all changes to assets and their configurations. Technical controls are deployed to record configuration changes: version control for code configurations, HIDS, AWS Cloudtrail, AWS Config. ISMS Policies are maintained that describe and enforce change management specific controls: Change Management Policy, Release Management Process, Project Management, Software Development Life Cycle.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: Figshare maintains a Vulnerability Management Policy that requires period detection, analysis and remediation of vulnerabilities for OS packages, third party libraries and managed web applications. Different tools/services are used in this process: Wazuh, Qualys, Debian Security Tracker, GitHub Security Advisories, OpenCVE. OS level CVEs are detected on a daily basis via automated scans performed by Wazuh (NVD and Debian Security Tracker CVE databases). Available security patches are applied weekly. Third party libraries vulnerabilities are analysed weekly via GitHub Security Advisories. Identified vulnerabilities are patched in every Release procedure. Web applications vulnerabilities scans are performed in every Release procedure.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: - 24/7 automated monitoring: all services internally and externally. All send automated events to our 24/7 on-call devops team. - OS level monitoring: HIDS software deployed across all systems to detect and alert for suspicious activity. Log all system level commands via Linux Audit module. - Application monitoring: APM solution to monitor performance and exception related metrics. - Vulnerability management: antivirus solution and OS security scans. Weekly maintenance routines for OS patching and 3rd party libraries’ security assessments. - Real-time analysis: Multiple tools analyse and detect anomalies across infrastructure. Logs collected and centralised for long term storage / analysis.
• Incident management type: Complies with a recognised standard, for example, CSA CCM v4.0 or ISO/IEC 27035:2011 or SSAE-18 / ISAE 3402
• Incident management approach: Security incidents are classified according to their impact on operations, the critical level of the system impacted and the level of sensitivity of the compromised data. Once a security incident has been found, the response stage will involve restoring operations and diminishing the impact of the vulnerabilities unveiled. Activities performed during the response stage vary according to the type of incident and to the security level. Further details are available in Figshare’s Incident Management Procedure document, available upon request.
• Post-quantum cryptography secure: Yes

Secure development

• Approach to secure software development best practice: Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v4.0)

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: No
• Free trial available: Yes
• Description of free trial: Freely available figshare.com site with only basic metadata, a few Open Licence choices, no branding, no Groups etc. Or we can create a free basic custom test portal on request, with more features (e.g. Groups, custom metadata, review workflow), with a few manually-created admin and user accounts.
• Link to free trial: https://figshare.com/

Discount percentage by annual call-off contract value (excluding VAT)

• Less than £250,000: 0%
• Between £250,000 and £500,000: 0%
• Between £500,001 and £1,000,000: 0%
• Between £1,000,001 and £2,500,000: 5%
• Between £2,500,001 and £5,000,000: 10%
• Over £5,000,001: 15%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: National Quality Assurance, U.S.A.
• ISO/IEC 27001 accreditation date: Wednesday 4 January 2023
• What the ISO/IEC 27001 doesn’t cover: Digital Science Statement of Applicability includes all controls except A.14.2.7 (27001)/A.6.11.2.7 (27701) - Outsourced Development. This is on the basis that Digital Science does not outsource development.
• ISO 28000:2022 certification: No
• ISO 9001 certification: No
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: No
• Cyber Essentials Alternative: In relation to the services you do not have a current and valid Cyber Essentials certificate which has been awarded by one of the government approved Cyber Essentials accreditation bodies but you are working towards gaining it, and will be in a position to confirm that you have been awarded a current and valid Cyber Essentials certificate by one of the government approved accreditation bodies within 12 months of the date of award.
• Cyber essentials plus: No
• Cyber Essentials Alternative: None of the criteria
• Other security certifications: No

Social value

• Section B - Commitment for Future: Delivery:

  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 1: Fair work: That offers fair wages and good working conditions. Help people get a job, stay in work, and progress in their careers, with good employment opportunities across the country. Notes: Where there is a large proportion of labour costs in the contract, commercial teams should consider MAC in Outcome 1 as a priority

    • Providing opportunities for, and measuring and monitoring of, staff workforce conditions over time, including employee engagement, involvement in decision-making and satisfaction and adapting to any changes in the results, with clear processes for acting on issues identified
    • Monitoring of employee engagement rates (by protected characteristic) and, where necessary, the development of actions to ensure all voices are heard across the diversity of the workforce
    • Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
    • Understanding of the modern slavery risks and issues affecting the market, industry, sector or country (of origin or of source) relevant to the contract, and the workforce in the supplier’s own organisation and those of its key subcontractors

  • Mission: Make Britain a clean energy superpower: To cut bills, create jobs and deliver security with cheaper, zero-carbon electricity by 2030, accelerating to net zero

    Policy Outcome 4: Sustainable procurement practices: Reducing carbon footprints, minimising waste, and promoting the use of clean energy and green technologies.

    • Understanding of opportunities for additional environmental benefits delivery in the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies

  • Mission: Break down barriers to opportunity: By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain

    Policy Outcome 6: Employment and training: For those who face barriers to employment

    • Understanding of the issues affecting the representation of disabled people in the workforce in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
    • Understanding of the issues affecting inequality in employment, skills and pay in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors. Measures to tackle inequality in employment, skills and pay in the contract workforce

  • Mission: Build an NHS fit for the future: That is there when people need it; with fewer lives lost to the biggest killers; in a fairer Britain, where everyone lives well for longer.

    Policy Outcome 8: Increasing productivity through physical and mental wellbeing: In the supply chain and communities in the relevant area.

    • Understanding of issues relating to health and wellbeing, including physical and mental health, in the contract workforce

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at rfp@digital-science.com. Tell them what format you need. It will help if you say what assistive technology you use.