MILLERSOFT LIMITED

Millersoft Apache Superset Managed Service

Millersoft provides a managed Apache Superset service, delivering secure deployment, configuration, operation, and support of the open-source data visualisation and analytics platform on government-aligned cloud infrastructure. The service enables users to explore, analyse, and visualise data through interactive dashboards without managing the underlying platform.

Features

• Managed deployment of Apache Superset
• Hosting on government-aligned cloud infrastructure
• Secure configuration and access controls
• Integration with multiple data sources
• Dashboard and chart management
• Role-based access and permissions
• Monitoring, patching, and upgrades
• Incident and change management
• Backup and configuration management
• Named support and service reviews

Benefits

• Quickly create interactive dashboards without specialist infrastructure skills
• Securely explore and visualise data from multiple sources
• Reduce operational overhead by outsourcing platform management
• Enable faster insight and decision-making through self-service analytics
• Maintain compliance with government security requirements
• Control access to data and dashboards by role
• Keep the platform up to date with minimal disruption
• Improve service reliability through proactive monitoring
• Scale analytics capability as user demand grows
• Teams to focus on data analysis rather than platform operations

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 accounts@millersoftltd.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

425610936271403

Contact

Calum Miller
0131 507 0256
accounts@millersoftltd.com

About your service

• Service categories:

  Systems Infrastructure Software

  System and service management

  • IT operations management
  • IT service management
• Multi cloud support: Yes

Service scope

• Software add-on or extension: No
• Cloud deployment model:
  • Public cloud
  • Private cloud
  • Community cloud
  • Hybrid cloud
• Service constraints: The managed Apache Superset service has some constraints buyers should be aware of. Planned maintenance windows are required for upgrades, patching, and configuration changes and are excluded from availability calculations. The service supports deployment only on agreed, government-aligned cloud infrastructure and does not include end-user device support. Custom application development and bespoke Superset feature development are out of scope unless agreed separately. Integration is limited to supported data sources and authentication methods. Support is provided for the Superset platform and configuration, but not for underlying data quality, query optimisation in source systems, or third-party tools outside the agreed service scope.
• System requirements:
  • Government-aligned cloud or on-premise infrastructure
  • Supported Linux operating system for hosting Superset
  • Network connectivity to data sources
  • Supported database engines for metadata storage
  • Secure authentication provider (for example LDAP or SSO)
  • TLS certificates for encrypted network traffic
  • Modern web browser for end users
  • Sufficient compute and memory resources
  • Secure storage for configuration and backups
  • Outbound internet access for updates and patches

User support

• Email or online ticketing support: Yes
• Support response times: Millersoft responds to questions in line with the agreed support level. Under standard support (9x5), questions and service requests are acknowledged within 1 business day, Monday to Friday, excluding UK public holidays. Responses are prioritised based on impact and urgency. For customers with enhanced 24x7 support, questions related to live service issues are acknowledged at any time, including weekends and public holidays, with faster response targets for high-severity issues. Non-urgent queries raised outside business hours are responded to during the next business day unless otherwise agreed.
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: EN 301 549
• Phone support: Yes
• Phone support availability: 9 to 5 (UK time), Monday to Friday
• Web chat support: No
• Onsite support: Yes, at extra cost
• Support levels: Millersoft provides tiered support levels for the managed Apache Superset service to meet different operational and business requirements. Standard Support (9x5) is included in the core service price. It provides support during UK business hours, Monday to Friday, excluding public holidays. Standard support covers incident management, fault investigation, service requests, and general platform queries. Incidents are prioritised by severity with defined response targets. This level is suitable for non-critical environments and routine analytics use and is included in the monthly service charge. Enhanced Support (24x7) is available as an optional add-on for business-critical services. This provides round-the-clock support, including evenings, weekends, and public holidays, with faster response times for high-severity incidents. Enhanced support is typically priced between £1,500 and £4,000 per month, depending on service scale and complexity. For customers requiring closer engagement, Millersoft can provide a named Technical Account Manager (TAM) or senior Cloud Support Engineer. This role acts as a primary technical point of contact, coordinates changes and upgrades, supports capacity planning, and leads regular service reviews. TAM services are optional and priced separately, usually on a monthly retained basis.
• Support available to third parties: Yes

Onboarding and offboarding

• Getting started: Millersoft helps users start using the managed Apache Superset service through a structured onboarding and enablement process designed to minimise time to value. The process begins with an onboarding and discovery phase to understand user requirements, data sources, security needs, and reporting objectives. Based on this, Millersoft deploys and configures Apache Superset in line with the customer’s cloud environment and governance requirements. Users are provided with clear onboarding documentation, including service overviews, architecture diagrams, access instructions, and guidance on connecting data sources and building dashboards. Documentation is written in plain English and supports both technical and non-technical users. Millersoft delivers remote onboarding sessions to introduce users to the Superset interface, demonstrate dashboard creation and data exploration, and explain support and operational processes. Optional training workshops can be delivered remotely or onsite, covering analyst and administrator topics such as dataset modelling, SQL Lab usage, security configuration, and dashboard best practice. Ongoing support is available through agreed support channels, with access to experienced engineers who can answer questions and assist users during early adoption. Documentation is maintained and updated throughout the service lifecycle to support continued use and self-service analytics.
• Service documentation: Yes
• Documentation formats: HTML
• End-of-contract data extraction: When the contract for the Millersoft managed Apache Superset service ends, users are supported through a clear and controlled data extraction process to ensure continuity and avoid vendor lock-in. Apache Superset stores configuration and analytical content using open, documented formats and standard databases, enabling customers to retain ownership of their data and assets. Users can extract their data by exporting dashboards, charts, datasets, and SQL queries using Superset’s built-in export functionality and supported APIs. Underlying data remains in customer-owned data sources and is not stored exclusively within Superset, allowing users to continue accessing their data independently of the service. Metadata and configuration information can also be exported to support migration or re-deployment. Millersoft provides off-boarding documentation detailing available export methods and supports customers in planning extraction activities. Where required, Millersoft can assist with coordinated exports or provide guidance for transferring content to a successor platform, subject to agreed scope. All data extraction is performed over secure, authenticated connections. Following confirmation that exports are complete, Millersoft removes customer access and securely decommissions the service in line with agreed retention and security policies, ensuring an orderly and secure exit.
• End-of-contract process: At the end of the contract, Millersoft follows a defined and transparent end-of-contract process for the managed Apache Superset service. The process begins with an agreed off-boarding plan that sets out timelines, responsibilities, and exit activities. Millersoft supports customers in exporting dashboards, charts, datasets, queries, and configuration information using Superset’s standard export tools and APIs. Documentation is provided to guide customers through the exit process and support transition to a successor platform or internal service. Once the customer confirms that data and configuration extraction is complete, Millersoft removes user access, decommissions the Superset environment, and securely deletes any remaining service data in accordance with agreed retention and security policies. Knowledge transfer and configuration handover are provided to enable an orderly transition. The contract price includes standard off-boarding support, access to exit documentation, guidance on exporting Superset content, and reasonable assistance during service termination within the agreed contract term. Additional costs may apply for activities outside the standard scope, such as large-scale content migration, bespoke export tooling, extended exit support beyond agreed timescales, onsite assistance, or accelerated termination requests. Any additional costs are agreed with the customer in advance to ensure transparency.
• Documentation accessibility standard: None or don’t know
• How the documentation is accessible: Millersoft ensures that onboarding and off-boarding documentation for the managed Apache Superset service is easy to access, secure, and available throughout the service lifecycle. Documentation is provided in electronic format and made available through secure, access-controlled channels agreed with the customer, such as a customer portal, secure document repository, or encrypted file sharing service. Access is restricted to authorised customer users using role-based permissions. Onboarding documentation includes service overviews, architecture diagrams, security responsibilities, access procedures, and guidance on using Superset to connect data sources, build dashboards, and manage users. Off-boarding documentation explains the end-of-contract process, data and dashboard export options, configuration handover, and service termination steps. Content is written in clear, plain English and structured to support both business users and technical administrators. Documentation is version-controlled and maintained as living artefacts, ensuring users always have access to the latest approved versions. Updates are communicated through service reviews or change notifications. Where required, documentation can be provided in formats suitable for internal assurance, audit, or governance activities. Millersoft also offers walkthrough sessions to accompany the documentation, helping users understand and apply the information effectively during onboarding and off-boarding.

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: The desktop experience provides full functionality, including dashboard creation, data exploration, chart editing, and administration features. On mobile devices, Superset supports responsive access for viewing dashboards and charts, allowing users to monitor metrics and review insights on the move. However, complex tasks such as creating or editing dashboards, managing datasets, or administering the platform are limited or not supported on mobile devices. For best usability and full feature access, a desktop or laptop browser is recommended.
• Service interface: Yes
• User support accessibility: None or don’t know
• Description of service interface: The managed Apache Superset service is accessed through a secure, web-based interface using a modern browser. The interface provides interactive dashboards, charts, and data exploration tools that allow users to analyse and visualise data without writing code. Users can filter, drill down, and explore datasets using intuitive controls. Role-based access controls determine which dashboards, datasets, and features each user can access. Administrative users can manage data sources, users, roles, and security settings through the same interface. The service also exposes APIs to support integration with other systems and automation where required.
• Accessibility standards: EN 301 549
• Accessibility testing: Millersoft doesn't claim formal certification against accessibility standards, and Apache Superset has not been subject to dedicated, supplier-led usability testing with users of assistive technology. However, accessibility considerations are addressed through a combination of upstream platform capabilities, browser support, and operational good practice. Apache Superset is a web-based application designed to run in modern browsers, which provide built-in support for common assistive technologies such as screen readers, keyboard navigation, zoom, and high-contrast display modes. Superset uses standard web technologies and components, enabling compatibility with widely used assistive tools where supported by the browser and operating system. Millersoft supports customers by configuring the service to maximise accessibility where possible, for example by ensuring compatibility with supported browsers, avoiding unnecessary customisation that could reduce accessibility, and enabling role-based access to simplify user interfaces. We also work with customers to understand user needs and can support reasonable adjustments, such as alternative dashboard layouts or simplified views, within the capabilities of the platform. Feedback from users, including those using assistive technologies, is captured through support channels and service reviews and used to inform configuration changes or improvements. Where accessibility limitations are identified, Millersoft works with customers to identify practical mitigations or alternative access approaches.
• API: Yes
• What users can and can't do using the API: The managed Apache Superset service provides APIs that allow users to interact with and automate aspects of the platform in a controlled manner. Users can use Superset’s REST APIs to authenticate, query metadata, manage dashboards and charts, and integrate Superset content into external applications. These APIs support automation of reporting, embedding dashboards, and synchronising metadata with other systems. Users cannot use the API to provision the underlying Superset service or infrastructure. Initial service setup, including platform deployment, core configuration, networking, and security baselines, is performed by Millersoft as part of the managed service to ensure consistency and security. Authorised users can make changes through the API within the boundaries of their assigned roles. This includes creating or updating dashboards, charts, and datasets, managing saved queries, and triggering refreshes where supported. Role-based access controls ensure users can only modify content they are permitted to manage. Users cannot use the API to change platform-wide settings, authentication mechanisms, or infrastructure resources. Changes that could affect service stability, security, or other users—such as upgrades, scaling, or security configuration changes—are managed through Millersoft’s change management process rather than directly via APIs.
• API documentation: Yes
• API documentation formats:
  • Open API (also known as Swagger)
  • HTML
• API sandbox or test environment: No
• Customisation available: Yes
• Description of customisation: Users can customise the Millersoft managed Apache Superset service to suit their data analysis, reporting, and governance requirements while retaining the benefits of a managed platform. Customisation includes the creation and configuration of dashboards, charts, datasets, and SQL queries, allowing users to tailor visualisations to their specific data sources and business needs. Users can customise filters, parameters, visual themes, and dashboard layouts to support different audiences and use cases. Customisation is carried out through Superset’s web interface and supported APIs. Authorised users can connect approved data sources, define datasets, build charts, and assemble dashboards using self-service tools. Automation and integration with external systems can be achieved through Superset APIs where appropriate. Operational customisation, such as adjusting refresh schedules, alerting thresholds, and access permissions, is supported within agreed service boundaries. Customisation rights are controlled through role-based access controls. Business users can interact with and explore dashboards, while power users and analysts can create and modify content. Administrative users, approved by the customer and Millersoft, can manage users, roles, and data source connections. Changes affecting platform configuration, infrastructure, or security controls are restricted to Millersoft engineers and managed through formal change processes.

Scaling

• Independence of resources: Millersoft ensures users are not affected by other users’ demand through logical and operational isolation. Apache Superset environments are deployed as dedicated instances per customer, preventing cross-tenant contention for compute, memory, or storage resources. Capacity is sized based on agreed usage patterns, with resource limits applied to control workload impact. Where shared infrastructure is used, isolation is enforced using containerisation, namespace separation, and resource quotas. Continuous monitoring identifies performance pressure early, allowing proactive scaling or optimisation. This approach ensures predictable performance, protects availability, and prevents one customer’s activity from degrading another customer’s service.

Analytics

• Service usage metrics: Yes
• Metrics types: The managed Apache Superset service provides operational and usage metrics to support service monitoring and optimisation. Metrics include service availability, response times, dashboard load performance, query execution times, and error rates. User activity metrics such as dashboard access, query frequency, and resource utilisation are monitored to support capacity planning. System metrics covering CPU, memory, and storage usage are collected to identify performance or scaling issues. Metrics are available through monitoring dashboards and logs, and summary reports may be provided as part of regular service reviews to support operational decision-making.
• Reporting types:
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request
• Resource tagging: Yes
• 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
• User control over data storage and processing locations: Yes
• Datacentre security standards: Complies with a recognised standard (for example CSA CCM version 4.0)
• Penetration testing frequency: At least every 6 months
• 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
  • Physical access control, complying with another standard
  • Encryption of all physical media
  • Scale, obfuscating techniques, or data storage sharding
• Data sanitisation process: Yes
• Equipment disposal approach: A third-party destruction service
• Data sanitisation type:
  • Data Erasure
  • Explicit overwriting of storage before reallocation / Secure Erase
  • Degaussing

Data importing and exporting

• Data export approach: Users export their data from the managed Apache Superset service using built-in export tools and supported APIs. Dashboards, charts, datasets, and saved queries can be exported in standard formats for reuse or migration. Superset does not store source data permanently; underlying data remains in customer-owned data sources and can be accessed independently. Metadata and configuration can also be exported to support re-deployment. All exports are performed over secure, authenticated connections. Millersoft provides documentation and guidance to support data export and can assist with planning or execution where required, ensuring users retain full control of their data. Dump to S3 available.
• Data export formats: CSV
• Data import formats: CSV

Data-in-transit protection

• Data protection between buyer and supplier networks:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Legacy SSL and TLS (under version 1.2)
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Legacy SSL and TLS (under version 1.2)

Availability and resilience

• Guaranteed availability: Millersoft guarantees service availability for the managed Apache Superset service through defined Service Level Agreements (SLAs) agreed with customers. Unless otherwise specified in the contract, the service has a target availability of 99.5% per calendar month, excluding planned maintenance and customer-caused outages. Availability applies to the Superset application interface and agreed supporting components and is measured using service monitoring and health checks. The service is designed to minimise unplanned downtime through monitoring, resilient deployment patterns, and controlled change management. Planned maintenance activities, such as upgrades or security patching, are scheduled in advance and communicated to customers and are excluded from availability calculations. If availability falls below the agreed SLA in a given month, customers may be entitled to service credits. Service credits are calculated as a percentage of the monthly service charge, based on the level of availability achieved. Credits are applied as an adjustment to future invoices and are not paid as cash refunds. Total service credits are capped to ensure they remain proportionate. Service credits are the customer’s sole and exclusive remedy for availability SLA breaches. Repeated or significant SLA failures trigger a service review and corrective action plan to improve service reliability.
• Approach to resilience: Millersoft designs the managed Apache Superset service to be resilient in accordance with the UK Government’s cloud security principles, including Asset Protection and Resilience. At a platform level, the service is deployed on resilient, government-aligned cloud infrastructure that supports high availability, fault tolerance, and rapid recovery. Detailed design information about physical data centre setup, redundancy, and geographic resilience is available on request to support assurance activities. The Superset application is deployed with redundancy and monitoring to handle component failures without service interruption. Load-balancing and health checks ensure that user sessions are routed to healthy instances and that service disruptions are minimised. Underlying infrastructure services (compute, networking, storage) benefit from the cloud provider’s built-in resilience features, such as automated failover, distributed storage, and network isolation. Millersoft’s operational practices further enhance resilience through continuous monitoring of system health, automated alerts, and defined incident response processes that detect and respond to potential issues quickly. Regular backups of configuration and metadata support recovery from data corruption or operational errors. Capacity planning and scaling controls mitigate performance degradation under increased load, while controlled change management processes reduce the risk of outages during maintenance.
• Outage reporting: Millersoft reports service outages and significant service issues through clear, timely, and structured communication channels agreed with customers. Outages are identified through continuous monitoring and alerting of the platform and supporting infrastructure. When an outage or service degradation is detected, it is logged, assessed, and classified by severity. Customers are notified of high-severity outages via email alerts to agreed operational and service contacts. Initial notifications provide a summary of the issue, affected components, and immediate actions being taken. During an ongoing outage, Millersoft provides regular status updates at defined intervals, particularly for critical incidents, to keep customers informed of progress toward restoration. Where agreed, customers may be provided access to a service status dashboard or regular service reports showing current and historical availability, incidents, and trends. This information supports operational visibility and service assurance. At present, outage notifications are not exposed via a public API; however, incident information can be shared through agreed reporting formats or integrated into customer service management processes on request. Once an outage is resolved, customers receive confirmation of service restoration. For significant incidents, Millersoft provides a post-incident report detailing the root cause, impact, resolution actions, and any measures implemented to reduce the risk of recurrence.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Dedicated link (for example VPN)
  • Username or password
• Access restrictions in management interfaces and support channels: Millersoft restricts access to management interfaces and support channels using role-based access control and the principle of least privilege. Administrative access is limited to authorised personnel with a legitimate business need and protected using strong authentication, including multi-factor authentication where supported. Management interfaces are not publicly exposed and are accessible only via private networks, VPNs, or IP allow-listing. Support channels are access-controlled, and identity verification is required before sensitive actions are performed. All administrative access and support activities are logged and reviewed regularly to maintain security and accountability.
• Access restriction testing frequency: At least every 6 months
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Dedicated link (for example VPN)
  • Username or password

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: User-defined

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: No
• Security governance approach: Millersoft approaches security governance through defined policies, clear accountability, and ongoing oversight aligned with UK Government Cloud Security Principles. Security responsibilities are assigned to senior management and operational roles, ensuring ownership and decision-making authority. Policies cover risk management, access control, incident management, change management, and data protection, and are reviewed regularly. Security risks are identified and assessed through monitoring, vulnerability management, and service reviews, with appropriate controls applied. Governance activities include regular reviews of security posture, incident trends, and compliance requirements, ensuring security considerations are embedded throughout the service lifecycle.
• Information security policies and processes: Millersoft follows a structured set of information security policies and processes designed to protect the confidentiality, integrity, and availability of customer data and services. Our information security framework is aligned with industry good practice and the UK Government Cloud Security Principles. We maintain documented policies covering information security governance, risk management, access control, acceptable use, incident management, vulnerability management, change and configuration management, business continuity, and data protection. These policies define clear roles and responsibilities across the organisation. Overall accountability for information security sits with senior management, with day-to-day responsibility delegated to designated security and operational leads. Security risks are identified and assessed through regular service reviews, vulnerability monitoring, incident analysis, and change impact assessments. Identified risks are prioritised and managed using appropriate technical and organisational controls. Access to systems and data is controlled using role-based access and the principle of least privilege, supported by strong authentication. Compliance with security policies is ensured through documented procedures, staff training, and operational controls embedded into service delivery. Security events and incidents are reported through defined escalation paths and reviewed to identify lessons learned. Policies and processes are reviewed periodically and updated to reflect changes in risk, technology or regulatory requirements.
• Software Security Code of Practice: Yes

Operational security

• Configuration and change management standard: Supplier-defined controls
• Configuration and change management approach: Millersoft operates controlled configuration and change management processes to maintain service security and stability. Service components are documented and tracked throughout their lifecycle, including configuration baselines, versions, and dependencies. Changes are proposed through a formal change process and assessed for impact on security, availability, and performance before approval. Security considerations include access controls, data protection, and vulnerability exposure. Changes are tested in non-production environments where appropriate and implemented during agreed maintenance windows. All changes are logged and reviewed to support auditability, rollback, and continual service improvement.
• Vulnerability management type: Undisclosed
• Vulnerability management approach: Millersoft operates a structured vulnerability management process aligned with industry good practice and government cloud security principles. Potential threats are assessed using upstream project security advisories, CVE databases, dependency monitoring, and reviews of service configuration and exposure. Vulnerabilities are prioritised based on severity, exploitability, and impact on confidentiality, integrity, and availability. Security patches and upstream fixes are deployed promptly following validation, with critical vulnerabilities addressed as soon as practicable. Where immediate patching is not possible, mitigating controls are applied. Threat intelligence is sourced from vendor advisories, open-source security announcements, CVE feeds, and relevant security research.
• Protective monitoring type: Undisclosed
• Protective monitoring approach: Millersoft operates continuous protective monitoring to identify potential security compromises across the service. System, application, and access logs are centrally collected and monitored for anomalous behaviour, unauthorised access attempts, and policy violations. Automated alerts highlight suspicious activity and service degradation. When a potential compromise is identified, incidents are triaged promptly, affected components may be isolated, and corrective actions are taken to contain and remediate the issue. High-severity security incidents are prioritised for immediate investigation and response. We respond to suspected security incidents as soon as practicable, with critical incidents addressed without delay through a defined incident response process.
• Incident management type: Undisclosed
• Incident management approach: Millersoft operates defined incident management processes aligned with industry good practice. Pre-defined procedures exist for common events such as service outages, performance degradation, and security incidents, ensuring consistent and timely response. Users report incidents through agreed support channels, including email or a secure support portal, where incidents are logged and prioritised by severity and impact. Customers receive regular status updates during incident resolution. For significant incidents, Millersoft provides incident reports detailing the issue, impact, root cause, resolution actions, and corrective measures to prevent recurrence.
• Post-quantum cryptography secure: No

Secure development

• Approach to secure software development best practice: Supplier-defined process

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: No
• Free trial available: No

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: 0%
• Between £2,500,001 and £5,000,000: 0%
• Over £5,000,001: 0%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: No
• 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: In relation to the services you do not have a current and valid Cyber Essentials Plus 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 Plus certificate by one of the government approved accreditation bodies within 12 months of the date of award.
• 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

    • New or retained jobs on the contract workforce in the relevant area that meet the criteria set out in MAC 1b, 1c and 1d
    • New apprenticeships on the contract workforce in the relevant area that meet the criteria set out in MAC 1b
    • 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
    • Plans to engage the contract workforce in deciding the most important workplace issues to address
    • Ensuring new workers are informed of their right to join a trade union
    • 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
    • Employment contracts that reflect actual hours worked; steps taken to ensure employees understand their contracts and have the ability to review and adjust them if actual hours regularly exceed contracted hours
    • Activities that support an environment where staff are educated about, and feel empowered to, address their physical wellbeing
    • Activities that support an environment where staff are educated about and feel empowered to report and address bullying and harassment
    • Activities to cascade good practice on fair working conditions throughout the supply chain
    • Offer a pay and leave entitlement to all eligible staff who become kinship carers, ideally equivalent to statutory adoption pay and leave
    • Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
    • Monitoring and reporting of gender and ethnicity pay gaps and plans to address them where necessary
    • Entitlement to sick pay for the contract workforce, with provision in place for any staff who do not meet the earnings threshold for statutory sick pay, payment of sick pay from day one of absence and payment of staff on the contract workforce who are off sick a replacement income of 100% of their usual earnings for as long as possible
    • Plans for an appropriate income replacement policy for staff who are required to spend time away from work to care for a sick dependent or close relative
    • Understanding of in-work progression issues affecting 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 support in-work progression to help people in the contract workforce, to move into higher paid work by developing new skills relevant to the contract
    • Support for the contract workforce by providing career advice, and providing opportunities for staff working on the contract with in-work progression career development into known skills shortages or high growth areas
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Volunteering opportunities for staff
    • 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
    • Measures to identify, mitigate and manage modern slavery risks relating to the contract and how these will be implemented
    • Outline policies and practices to be applied to or put in place for the contract to mitigate and manage modern slavery risks, including: Pre-employment checks, recruitment practices. Workplace conditions, safeguarding plans and processes in place and regular monitoring with relevant groups considered, which may include sampling
    • How these flow down the supply chain and are monitored Illustrative examples include reporting, site visits, audits, etc.
    • How to ensure business decisions re: price/cost, short lead times, payment timescales do not create modern slavery risks in the supply chain
    • How the supplier will work with NGOs, trade unions or other businesses to address modern slavery risk
    • Means of influencing staff, suppliers, customers, communities and/or any other appropriate stakeholders with respect to modern slavery risks relating to the contract

  • 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 2: Skills for growth: Supporting growth sectors and addressing skills gaps.

    • Understanding of employment and relevant skills issues, and of the education and training issues relating to the contract. Illustrative examples: demographics, skills shortages, new opportunities in high growth sectors, geographic/local community and skills/employment challenges
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Activities to support relevant sector related skills growth and sustainability in the contract workforce. Illustrative examples: careers talks, curriculum support, literacy support, safety talks and volunteering
    • Delivery of apprenticeships, supported internships and T Level industry placement opportunities (Level 2, 3 and 4+) in relation to the contract

  • 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 3: Resilient, innovative and flexible supply chains: Support economic growth through enabling resilient businesses, opportunities for small businesses and voluntary, community and social enterprises

    • Understanding of the types of businesses in the market and the level of participation by new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
    • Activities to identify opportunities to open up sub-contracts under the prime contract to a diverse range of businesses, including new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
    • Plans for engaging a diverse range of businesses in engagement activities prior to appointing subcontractors (including activities prior to award of the main contract and during the contract term)
    • Activities that demonstrate a collaborative way to work with a diverse range of businesses as part of the supply chain
    • Advertising of supply chain opportunities openly and to ensure they are accessible to a diverse range of businesses, including advertising all subcontracting opportunities on Contracts Finder
    • Ensuring accessibility to contracting and subcontracting opportunities for disabled business owners and employees
    • Structuring of the supply chain selection process to ensure fairness (e.g. anti-corruption) and encourages participation by a diverse range of businesses, including with regard to new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutual
    • Understanding of local demographics, needs and opportunities for the co-design of the goods, services and works to be delivered under the contract
    • Methods for engaging with different parts of the community (including the education system and charities representing the community) and how communities come together to inform decisions, strategy and projects to leave a positive legacy for future generations
    • Measures to involve local stakeholders and/or users in design (e.g. in the design of services, systems, products or buildings)
    • Plans for positive actions with community groups.
    • Measures for making facilities used in the delivery of the contract available for community groups, education or training
    • Measures to engage users and communities and build relationships to increase community integration build trust and influence how the contract is delivered
    • Plans to respond flexibly and adapt approaches to community engagement and initiatives
    • Support for community-led initiatives relevant to the contract. Illustrative examples: improving transport links; reducing loneliness; helping with English language proficiency; and facilitating social mixing among people with different backgrounds
    • Collaborating with anchor institutions and community groups to make facilities available for education, training or community events

  • 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
    • Collaborative ways of working with the supply chain to deliver additional environmental benefits in the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
    • Delivery of additional environmental benefits through the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
    • Understanding of how to influence staff, suppliers, customers, communities and/or any other appropriate stakeholders through the delivery of the contract to support climate and nature protection and improvement
    • Activities to reconnect people with the environment and increase awareness of ways to protect and enhance it

  • 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 employment and skills issues, and of the skills and employment shortages of high growth sectors relating to the contract
    • Creation of employment opportunities particularly for those who face barriers to employment, such as prison leavers, care leavers and/or who are located in deprived areas, and for people in industries with known skills shortages or in high growth sectors
    • Delivery of training schemes and programmes to address any identified skills gaps and under-representation in the workforce for the contract (e.g. prison leavers, care leavers, kinship carers, disabled people)
    • Advertising, promotional and outreach activities designed to raise awareness of the offer to reach the target cohort
    • 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
    • Collection of the views and expertise of disabled people and their representative organisations on successfully supporting disabled employees or applicants
    • Inclusive and accessible recruitment practices, and retention-focused activities, including those provided in the Guide for line managers on recruiting, managing and developing people with a disability or health condition
    • Introducing transparency to pay and reward processes
    • Offering a range of quality opportunities with routes of progression if appropriate, e.g. T Level industry placements, students supported into higher level apprenticeships.
    • Working conditions which promote an inclusive working environment and promote retention and progression
    • Other measures to provide equality of opportunity for disabled people and those with health conditions into employment, including becoming a Disability Confident employer and inclusion of supported businesses in the contract supply chain
    • 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
    • Inclusive and accessible development practices, including guidance for line managers on recruiting, managing and developing people with a disability or health condition

  • 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 7: Creating a pipeline of opportunities: For the contract workforce, reducing barriers to entry for under-represented groups.

    • Understanding of the issues affecting the development of new skills by target cohort
    • Understanding of the underlying factors affecting improvements to reduce barriers to entry and training schemes for the target cohort(s) related to the contract workforce
    • Other measures to offer development opportunities for the target cohort(s) in the contract workforce
    • Advertising, promotional and outreach activities designed to raise awareness of the offer to reach the target cohort
    • Understanding of issues relating to entering the contract workforce
    • Creation of outreach activities to create a pipeline of employees for the future contract delivery
    • Content of the outreach activity is designed to suit the target cohort
    • Advertising, promotional and outreach activities designed to raise awareness of the offer to reach the target cohort

  • 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
    • Understanding barriers to access to health and social care services or employment opportunities e.g. digital inclusion
    • Inclusive and accessible recruitment practices, development practices and retention policies that support-focused activities including those provided in the Guide for line managers on recruiting, managing and developing which support people with a disability or health condition
    • Actions to invest in the physical and mental health and wellbeing of 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 accounts@millersoftltd.com. Tell them what format you need. It will help if you say what assistive technology you use.