ENTSERV UK LIMITED

DXC Technology - Managed Container Services

Managed Container Services provides fully managed, enterprise‑grade container platforms across on‑premises and multi‑cloud environments. DXC designs, deploys, operates, secures, monitors, upgrades, and supports container platforms with defined SLAs, lifecycle management, optional add‑ons, and scalable support models enabling secure, resilient, and cost‑efficient application modernization.

Features

Fully managed container platform (OpenShift, Tanzu, Rancher)
Design, deployment, and onboarding services
24×7 monitoring and incident management
Defined service tiers and SLAs up to 99.9%
Patch management and platform upgrades
Backup and restore for platform components
Capacity and performance management
Embedded enterprise‑grade security controls
Multi‑cloud and on‑premises support
Optional add‑on services (DR, security, service mesh)

Benefits

Reduced operational complexity for container platforms
Improved platform availability and resilience
Faster application delivery and modernization
Predictable and scalable cost model
Enterprise‑grade security and compliance support
Reduced risk through standardized operations
Flexibility to run workloads across clouds and data centers
Access to skilled container and cloud experts
Always‑current platform with evergreen updates
Ability to focus teams on application development, not infrastructure

Service documents

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

Framework

G-Cloud 15

Service ID

Contact

ENTSERV UK LIMITED Richard Eckersley
Telephone: +447825113627
Email: richard.eckersley2@dxc.com

About your service

Service categories

PaaS

AI Platforms

AI life cycle
AI software services

Service scope

Service constraints: Underlying infrastructure (on‑prem or cloud) is out of scope for this service. Client or DXC supplied (extra offering).
Mandatory prerequisite: DXC professional services for design and deployment.
Service covers the container platform, not customer applications or code.
Platform licenses and third‑party subscriptions are customer‑owned or provided at extra cost.
Service scope depends on selected package; Break‑Fix includes no SLAs.
Support and SLAs apply only within chosen service windows and tiers.
Major upgrades, architecture changes, and excess requests may incur extra cost.
Security is shared; advanced security features are optional add‑ons.
Disaster recovery is optional and not included by default.
System requirements: Customer/DXC‑provided compute infrastructure private or public cloud

Network connectivity, DNS, firewall rules, and routing.

Sufficient storage for platform operations, backups, and optional persistent volumes

Secure connectivity between customer environment and DXC
Cloud deployment model: Public cloud

Private cloud

Community cloud

Hybrid cloud

User support

Email or online ticketing support: Yes
Support response times: Time‑to‑response commitments for email or ticket (incident acknowledgment), within the selected service window:

Priority 1 (Critical): Acknowledgment within 30 minutes
Priority 2 (High): Acknowledgment within 2 hours
Priority 3 (Medium): Acknowledgment within 8 hours
Priority 4 (Low): Acknowledgment within 24 hours

Response times apply to incidents logged via the service portal or email, and vary by service tier and support window. Break‑Fix packages have no SLA‑based response commitments.
User can manage status and priority of support tickets: No
Phone support: Yes
Phone support availability: 24 hours, 7 days a week
Web chat support: No
Onsite support: Yes, at extra cost
Support levels: Support Levels Overview
The service provides multiple support levels aligned to business criticality, service windows, and delivery locations.
Bronze Support
Provides standard operational support during business hours only (9×5). Coverage includes monitoring, incident acknowledgment, and resolution activities within the agreed service window. Suitable for non‑production or low‑criticality environments.
Silver Support
Extends Bronze by adding on‑call support outside business hours for Priority 1 and Priority 2 incidents. Business‑hour coverage remains the primary response model, with escalated handling for critical incidents. Designed for production workloads with moderate availability requirements.
SilverPlus Support
Offers extended 18×5 coverage plus on‑call support for Priority 1 and 2 incidents outside working hours. This level reduces response gaps for business‑critical platforms operating across extended time zones.
Gold Support
Delivers 24×7 continuous support for all incident priorities, with the highest operational responsiveness and SLA protection. Appropriate for mission‑critical platforms requiring constant availability and rapid incident handling.
Support levels determine response times, SLA applicability, and escalation handling. Availability SLAs apply only when supported by the selected service tier and package; Break‑Fix services operate without SLA commitments.
Support available to third parties: Yes

Onboarding and offboarding

Getting started: We guide users through a structured onboarding and enablement process designed to ensure a smooth and secure start.

Prerequisite Setup
We begin by completing design and deployment through professional services or validating an existing platform. Infrastructure, licenses, connectivity, and security prerequisites are confirmed.

Service Onboarding
DXC provisions the managed container platform and applies agreed configurations, security controls, RBAC policies, and monitoring. Users are registered as Authorized Representatives and granted role‑based access.

Access Enablement
Users receive access to the platform web console (e.g., OpenShift or Rancher), CLI, APIs, and the service portal for ticketing and requests. Authentication and IAM integration are validated.

Knowledge Transfer and Enablement
We provide documentation, operational guidelines, and optional enablement sessions covering platform usage, governance, and support processes.

Go‑Live Support
During early use, DXC provides close operational support and monitoring to verify stability, performance, and SLA alignment.

This approach ensures users can quickly onboard applications, operate within defined governance, and confidently use the platform while DXC manages the underlying service lifecycle.
Service documentation: Yes
Documentation formats: HTML

PDF
End-of-contract data extraction: When the contract terminates, users remain the sole owners of their applications, configurations, and data. During the agreed notice and transition period, users continue to access their environments using standard platform interfaces (web console, CLI, and APIs).
How data is extracted

Application data stored in persistent volumes can be exported or migrated using native Kubernetes, OpenShift, or Rancher tools and customer‑selected storage mechanisms.
Configuration data (manifests, namespaces, deployment definitions) can be retrieved through platform APIs, CLI commands, or CI/CD repositories.
Container images and logs can be copied or archived using platform‑supported methods.

DXC disengagement support
DXC supports a controlled handover, including knowledge transfer and removal of DXC administrative access at the agreed end date. Reasonable transition assistance is included; additional or extended support may be chargeable.
After termination
Once the disengagement is complete, DXC no longer accesses or retains customer data. Ongoing platform operation and data management become the customer’s responsibility.
End-of-contract process: Will be defined in the Statement of Work. Typically:
At the end of the contract, the service enters a controlled disengagement and transition phase. The customer remains the owner of all applications, configurations, and data throughout this period. Transition and handover During the agreed notice period, users continue to access the platform using standard interfaces (web console, CLI, APIs). DXC supports an orderly handover by providing reasonable knowledge transfer, documentation, and operational guidance to enable the customer to assume control. Data and access Customers extract or migrate their data using native platform capabilities. DXC does not retain customer data after termination. At the agreed end date, DXC removes its administrative access and ceases service operations. Service cessation Once the contract ends: Managed services, SLAs, monitoring, and support are discontinued Responsibility for platform operation, security, and maintenance transfers fully to the customer Any additional transition support beyond the standard scope may be provided on a time‑and‑materials basis Completion The disengagement is completed once access is transferred, DXC access is revoked, and contractual obligations are fulfilled.
Documentation accessibility standard: WCAG 2.2 AA

Using the service

Web browser interface: Yes
Using the web interface: Web Interface Capabilities & Limitations
Access to the service web interfaces (such as Red Hat OpenShift and SUSE Rancher) is controlled through a strict Role‑Based Access Control (RBAC) model. Permissions are granted by role and scope (cluster, project, namespace) to protect platform stability and SLAs.
How users can set up the service
Users can log in to the platform console and, within their RBAC scope, create projects or namespaces, deploy containerized applications, configure services and ingress, manage application configuration (secrets, config maps), and view logs, metrics, and platform health. Application onboarding and CI/CD integration are supported where enabled.
How users can make changes
Users may update, scale, restart, and redeploy applications, manage application resources, and monitor workloads through the console. Requests for capacity changes, new clusters, add‑ons, or platform changes are submitted via the service portal.
Limitations
Users cannot create or delete clusters, change cluster‑wide settings, modify underlying infrastructure, perform platform upgrades, or adjust SLA‑impacting configurations. Those actions are reserved for DXC under managed service governance.
Platform considerations

OpenShift: Strong separation between cluster‑admin and project roles; cluster‑admin access is typically DXC‑only.
Rancher: Centralized multi‑cluster view with enforced project and cluster scopes.
Web interface accessibility standard: WCAG 2.2 AA
Web interface accessibility testing: We rely on enterprise‑grade container platforms (for example, OpenShift and Rancher) that are developed and tested by their vendors to meet or exceed enterprise security, quality, and accessibility standards. These platforms receive regular functional upgrades and continuous bug fixes, which include usability and accessibility improvements delivered as part of standard product lifecycles. Our service preserves the native platform interfaces, allowing customers to benefit directly from vendor‑led enhancements while maintaining a secure, stable, and supportable environment.
API: Yes
What users can and can't do using the API: API Capabilities and Limitations
Access to APIs is governed by a strict Role‑Based Access Control (RBAC) model and platform‑native security controls. Users interact with APIs exposed by the underlying container platforms (such as OpenShift and Rancher) within their assigned roles and scopes.
What users can do via the API

Authenticate using platform‑supported mechanisms (tokens, certificates, IAM integration)
Deploy, update, scale, and delete applications and workloads within authorized namespaces/projects
Manage application resources such as services, ingress/routes, config maps, and secrets (RBAC‑scoped)
Query workload status, logs, metrics, and health information
Integrate CI/CD pipelines and automation tools with the platform APIs

What users cannot do via the API

Create, delete, or reconfigure clusters
Modify cluster‑wide settings, networking, storage architecture, or infrastructure
Perform platform upgrades, patches, or lifecycle operations
Change RBAC policies beyond their delegated scope
Alter SLA‑relevant or managed‑service configurations

Platform‑level APIs and privileged operations are restricted to DXC as part of the managed service. In summary, APIs enable full automation of application operations, while platform governance and stability remain centrally controlled.
API automation tools: Ansible

Terraform
API documentation: Yes
API documentation formats: PDF

Other
Command line interface: Yes
Command line interface compatibility: Linux or Unix

Windows

MacOS
Using the command line interface: What users can do (RBAC‑scoped)

Authenticate with kubeconfig/tokens and use kubectl / oc within authorized namespaces/projects.
Deploy, update, scale, and delete workloads: Deployments, StatefulSets, DaemonSets, Jobs/CronJobs.
Manage app resources: Services, Ingress/Routes, ConfigMaps, Secrets, PVC claims (where permitted).
Perform day‑2 ops: rollout (status/restart), logs, exec, port-forward, top, label/annotate, apply/patch.
Integrate automation (CI/CD) and GitOps flows; pull images from approved registries.
View cluster objects/metrics allowed by role; request changes via the Service Portal.

What users cannot do

Platform control: create/delete clusters, modify cluster‑wide configs, or perform upgrades/patching.
Infrastructure/network/storage: change CNI, node pools, storage classes/backends, or load balancer settings.
RBAC & policy: elevate privileges, alter cluster roles, bypass Pod Security/SCC, or create privileged pods without pre‑approval.
Security/compliance: disable audit, quotas, network policies, or mandatory scanners.
SLA‑impacting settings: alter managed configurations or maintenance windows.
Node access: SSH to nodes, modify OS/Kernel, or manage kubelets.

Notes:

OpenShift (oc) enforces strong separation between cluster‑admin (DXC) and project roles.
Rancher centralizes multi‑cluster access; cluster/project‑admin is restricted per contract.
All platform‑level actions flow through managed change and DXC governance.

Scaling

Independence of resources: We prevent impact between users within the same company through logical isolation and governance controls. Workloads are separated using namespaces, projects, or clusters, with RBAC ensuring users can access only their assigned resources. Resource quotas, limit ranges, and scheduling policies prevent teams from consuming excessive CPU, memory, or storage. Network policies isolate traffic between teams, and platform monitoring detects contention early. Capacity is planned and scaled based on demand, and platform changes are centrally managed to protect shared environments, ensuring one team’s usage does not disrupt others.
Usage notifications: Yes
Usage reporting: Email
Optimising consumption: Yes
Automatic scaling: Yes

Analytics

Infrastructure or application metrics: Yes
Metrics types: CPU

Disk

HTTP request and response status

Memory

Network

Number of active instances
Reporting types: API access

Real-time dashboards

Regular reports
Resource tagging: Yes
FOCUS resource tagging: Yes

Resellers

Supplier type: Reseller providing extra support
Organisation whose services are being resold: Many organisations

Staff security

Staff security clearance: Conforms to BS7858:2019
Government security clearance: Security Clearance (SC)

Asset protection

Knowledge of data storage and processing locations: Yes
Data storage and processing locations: United Kingdom

European Economic Area (EEA)

Other locations
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 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

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: 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 Erasure

Explicit overwriting of storage before reallocation / Secure Erase

Degaussing

Physical Destruction / Hardware containing data is completely destroyed

Backup and recovery

What’s backed up: Control plane configuration backed up daily

Platform configuration retention for defined periods

Restore of cluster control plane on request

Backup of container platform projects and metadata

Persistent storage backup via optional add‑on services

Disaster recovery coordination when DR add‑on is enabled

Vendor‑aligned backup tooling and best practices

Recovery procedures aligned with agreed RPO and RTO
Backup controls: Users control what backups are performed through service selection and configuration, within the managed‑service framework.

Users select backup options during onboarding (platform, storage, DR add‑ons).
Backup scope is defined per cluster and environment.
Persistent storage and DR backups are enabled only if purchased.
Changes to backup scope, frequency, or retention are requested via the service portal.
Application‑level data backup remains the user’s responsibility.
DXC implements and operates backup tooling and schedules.
Platform‑level methods and security controls are managed by DXC.
Datacentre setup: Multiple datacentres with disaster recovery

Multiple datacentres

Single datacentre with multiple copies

Single datacentre
Scheduling backups: Users contact the support team to schedule backups
Backup recovery: Users contact the support team
Backup and recovery: Yes
RPO/RTO: Yes

Data-in-transit protection

Data protection between buyer and supplier networks: Private network or public sector network

IPsec or TLS VPN gateway
Data protection within supplier network: TLS (version 1.2 or above)

IPsec or TLS VPN gateway

Availability and resilience

Guaranteed availability: The service provides enterprise‑grade availability guarantees of up to 99.9%, depending on the selected service package, service tier, and service window.
What is guaranteed

Cluster Availability SLA up to 99.9% for supported production clusters
Availability is measured as API endpoint responsiveness of the container platform
SLAs apply per cluster, measured on a monthly basis
Higher availability applies when appropriate architecture (HA, redundancy) is implemented

Conditions and scope

Availability SLAs apply only to managed container platforms, not to customer applications or data
SLAs are valid within the selected service window (e.g., Bronze, Silver, Gold)
Break‑Fix packages do not include availability SLAs
A baselining period applies before SLAs become enforceable
Availability depends on customer‑provided infrastructure meeting design requirements

Exclusions
Availability guarantees exclude:

Planned maintenance windows
Customer‑caused outages
Third‑party infrastructure failures
Events outside DXC’s control
Approach to resilience: Resilience by Design

Highly Available Control Plane: Clusters deployed with redundant masters/infra components; API responsiveness is the availability measure (SLA up to 99.9%).
Multi‑zone / Multi‑site Topologies: Support for on‑prem, cloud, and hybrid layouts; optional metro/remote DR architectures.
Disaster Recovery Options: Add‑on DR with defined RPO/RTO, including storage‑level replication (e.g., Portworx) and rehearsals.
Hardened Platform Baseline: Vendor‑supported Kubernetes (OpenShift, Tanzu, Rancher) with CIS‑aligned hardening, image scanning, and immutable components where applicable.
Automated Lifecycle & Patching: Controlled change windows, minor/major upgrades, and security patching to reduce risk and exposure.
Observability & SRE Practices: 24×7 monitoring, incident/problem management, RCA, capacity trending, and performance reporting.
Resource Safeguards: Quotas, limit ranges, and scheduling policies prevent noisy‑neighbor impact within and across namespaces.
Backup & Restore: Daily control plane configuration backups; optional persistent volume backups with defined retention.
Network & Fault Isolation: Namespaces/projects, network policies, and RBAC enforce blast‑radius reduction and least‑privilege access.
Partner‑aligned Architecture: Built with vendor best practices and premier support to avoid community‑only break/fix risk.

Result: A consistently patched, monitored, and isolated container platform with optional DR that sustains failures, minimizes blast radius, and speeds recovery—while DXC operates the platform and customers focus on applications.
Outage reporting: Outages are reported through automated monitoring and structured communication channels to ensure timely awareness and transparency.

Automated detection: Platform monitoring continuously checks cluster health and API availability. When an outage is detected, an incident ticket is automatically created.
Service portal updates: All outages are logged and tracked in the service portal, where users can view status, impact, and progress in real time.
Customer notifications: Affected customers are notified based on incident priority and their selected service window, via email and/or portal notifications.
Status updates: Regular updates are provided until resolution, following defined response and communication timelines.
Post‑incident reporting: For major incidents, a root cause analysis (RCA) and summary report are shared after resolution.

Identity and authentication

User authentication needed: Yes
User authentication: Multi-Factor Authentication (MFA)

Identity federation with existing provider (for example Google Apps)

Limited access network (for example PSN)

Dedicated link (for example VPN)

Other
Other user authentication: Users are authenticated using secure, enterprise‑grade identity controls integrated with the underlying container platforms (such as OpenShift and Rancher). Authentication supports centralized identity providers including corporate directories (e.g., LDAP or Active Directory), Single Sign‑On (SSO), and federated identity where available. Access is enforced through role‑based access control (RBAC), ensuring users only access permitted resources. For APIs and CLI access, short‑lived tokens, certificates, or service accounts are used. All authentication events are logged and monitored to support audit, security, and compliance requirements.
Access restrictions in management interfaces and support channels: Access to management interfaces and support channels is tightly controlled through Role‑Based Access Control (RBAC) and identity management. Only authorized customer representatives are granted access, authenticated via enterprise identity providers and secure credentials. Permissions are assigned by role and scope (cluster, project, or environment) to enforce least privilege.
Support channels (service portal and email‑to‑ticket) accept requests only from approved users, with request types limited by role. Privileged access is restricted to DXC operational staff and logged for audit purposes. All access is monitored and reviewed to maintain security and compliance.
Access restriction testing frequency: At least once a year
Management access authentication: Multi-Factor Authentication (MFA)

Identity federation with existing provider (for example Google Apps)

Limited access network (for example PSN)

Dedicated link (for example VPN)
Devices users manage the service through: Dedicated device on a segregated network (providers own provision)

Dedicated device on a government network (for example PSN)

Any device but through a bastion host (a bastion host is a server that provides access to a private network from an external network such as the internet)

Audit information for users

Access to user activity audit information: Users contact the support team to get audit information
How long user audit data is stored for: User-defined
Access to supplier activity audit information: Users contact the support team to get audit information
How long supplier audit data is stored for: User-defined
How long system logs are stored for: User-defined

Security governance

Named board-level person responsible for service security: Yes
Security governance certified: Yes
Security governance standards: CSA CSM version 4.0

ISO/IEC 27001
Information security policies and processes: We follow a comprehensive information security management framework aligned with ISO 27001, NIST Cybersecurity Framework, and industry best practices. Our security policies cover key domains including access control, data protection, incident response, vulnerability management, secure development, business continuity, asset management, and acceptable use. Policies are formally approved by executive leadership and reviewed annually or when significant changes occur. Our security governance model is led by the Chief Information Security Officer (CISO), who reports to senior executive leadership. The CISO oversees Security Operations, Governance/Risk/Compliance (GRC), and Architecture teams. These teams maintain policies, monitor adherence, and ensure alignment with regulatory and customer requirements. To ensure policies are followed, all staff complete mandatory annual security awareness training, with additional role-based training for privileged users and administrators. Automated technical controls enforce compliance, including MFA, role-based access control, encryption standards, monitoring, and patch governance. Internal audits, external assessments, penetration tests, and continuous monitoring validate that processes are effective. Any deviations or noncompliance are tracked through risk registers and remediation workflows. Regular reporting to senior leadership includes policy compliance metrics, audit findings, incident summaries, and improvement actions. Together, these measures ensure a robust and continuously improving security posture.

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: Configuration and change management are delivered through standardized, ITIL‑aligned processes. Platform components are documented as controlled configuration items and tracked centrally. Changes are requested via the service portal, assessed for risk, impact, and SLA implications, approved through defined governance, and implemented in approved maintenance windows. Standard changes are automated where possible; non‑standard or major changes follow formal change control and may require additional approval. All changes are tested, recorded, and reported, with rollback procedures in place to maintain platform stability and compliance.
Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
Vulnerability management approach: We use a continuous, risk‑based vulnerability management process aligned to industry best practices. Potential threats are assessed through automated security scanning, configuration reviews, and risk assessments across the container platform and its components. Vulnerabilities are prioritized based on severity, exploitability, and service impact.
Security patches and fixes are deployed promptly, typically via controlled patching cycles, with critical vulnerabilities addressed on an accelerated basis.
Threat intelligence is sourced from platform vendors (e.g., OpenShift, Rancher), security advisories (CVEs), industry security feeds, and internal operational monitoring, ensuring timely awareness and response.
Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
Protective monitoring approach: We use continuous platform, network, and security monitoring to identify potential compromises through alerting on anomalous behavior, security events, vulnerability indicators, and policy violations. Signals are correlated across logs, metrics, and security tooling to detect threats early.
When a potential compromise is identified, an incident response process is initiated: access may be restricted, affected components isolated, and remediation actions applied. The incident is investigated, and corrective measures are implemented to prevent recurrence.
Response times follow contracted incident priorities: critical incidents are acknowledged within 30 minutes, high‑priority within 2 hours, with ongoing updates until resolution.
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: We operate pre‑defined, ITIL‑aligned processes for common events and incident types, including platform outages, performance degradation, capacity issues, and security alerts. Automated monitoring can create incidents, and standard runbooks guide consistent response and resolution.
Users report incidents through the service portal or email‑to‑ticket, using authorized representatives. Incidents are classified by priority based on business impact.
Incident reporting includes real‑time status updates in the service portal, notification emails for major incidents, and post‑incident reports (including root cause analysis) for Priority 1 incidents after resolution.
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)

Separation between users

Virtualisation technology used to keep applications and users sharing the same infrastructure apart: Yes
Who implements virtualisation: Supplier
Virtualisation technologies used: VMware
How shared infrastructure is kept separate: Different organisations sharing the same infrastructure are kept apart through strong technical isolation and governance controls:

Dedicated or logically isolated environments: Customers use separate clusters or isolated namespaces/projects.
Strict RBAC: Role‑based access ensures users only see and manage their own resources.
Network isolation: Network policies prevent traffic between organisations.
Resource controls: CPU, memory, and storage quotas prevent one tenant impacting others.
Separate identities and credentials: Authentication and secrets are isolated per organisation.
Managed operations: Platform changes are centrally controlled to protect isolation and stability.

Energy efficiency

Energy-efficient datacentres: Yes
Description of energy efficient datacentres: DXC operates its data centers in alignment with the principles of the EU Code of Conduct for Energy Efficient Data Centers, focusing on reducing energy consumption, improving operational efficiency, and lowering environmental impact. While DXC does not publicly claim formal Participant status under the EU Code, our data-center practices incorporate the same core requirements. DXC implements an ISO 50001-certified Energy Management System across key facilities to continuously monitor, optimize, and manage energy use. This includes active tracking of power consumption, temperature, and cooling performance, with targeted actions to avoid energy spikes and reduce waste. Infrastructure is designed and operated to follow best practices such as efficient cooling, temperature optimization, virtualization, workload consolidation, and ongoing facility modernization. These measures directly support the objectives of the EU Code, including minimizing total energy demand and reducing carbon emissions. As a result, DXC has achieved significant reductions in Scope 1 and 2 emissions, demonstrating the effectiveness of its energy-efficiency program. Customers can rely on DXC data centers to operate with strong environmental governance, continuous efficiency improvements, and alignment with recognized European energy-efficiency standards.

Pricing

Discount for educational organisations: No
Free trial available: No

Discount

Provide your minimum discount applicable to your baseline prices: 0%

Formula for calculating price of your services

Which of the core deployment models you intend to offer

Public Cloud
Private Cloud

Public Cloud - Formula for calculating price of your services

Total Cost: The Total Cost for a buyer's call off requirement in a Public Cloud Deployment
=
Baseline Pricing: The baseline prices can be found in the pricing documents associated with the service offerings in Lot 1a.
Baseline Pricing - Web link: https://dxc.com/insights/knowledge-base/discover-how-to-cut-the-cost-of-cloud-migration
-
Minimum Discounting: 0%
+
Onboarding Activity: Onboarding costs may vary based on your specific requirements, please confirm with suppliers during the clarification process
+
Additional sources of cost: There are no additional sources of cost
-
Additional sources of cost reduction: There are no additional sources of cost reduction

Private Cloud - Formula for calculating price of your services

Total Cost: The Total Cost for a buyer's call off requirement in a Private Cloud Deployment
=
Baseline Pricing: The baseline prices can be found in the pricing documents associated with the service offerings in Lot 1a.
-
Minimum Discounting: 0%
+
Onboarding Activity: Onboarding costs may vary based on your specific requirements, please confirm with suppliers during the clarification process
+
Additional sources of cost: There are no additional sources of cost
-
Additional sources of cost reduction: There are no additional sources of cost reduction

Mandatory certifications

Are you are bidding to offer IaaS and/or PaaS as a reseller or are you in sole control of the infrastructure

Sole Control and also accredited to resell other providers' services

Cloud service suppliers you intend to resell with evidence

Organisation 1

Organisation name

Amazon Web Services

Website address/upload for organisation

Website address

https://aws.amazon.com/partners/dxc

Organisation 2

Organisation name

Google Cloud

Website address/upload for organisation

Upload

Provided

Organisation 3

Organisation name

Microsoft Azure

Website address/upload for organisation

Website address

https://marketplace.microsoft.com/en-us/partners/93f33571-550f-43cf-b09f-cd331338d086/overview

ISO 9001 certification

Provided

ISO 14001 certification

Provided

ISO 27001 certification

Provided

ISO 20000-1 certification

Provided

ISO 27017 certification

Provided

Are you bidding to provide services under Lot 1b or both Lot 1a and Lot 1b?

Yes

ISO 27018 certification

Provided

Cyber Essentials

Do you have a Cyber Essentials Plus certificate?: Yes
Cyber Essentials Plus certificate Number: 71a0fb97-216d-4781-914b-3aaf2455c8f2

Non-mandatory Standards and certifications

ISO 28000:2022 certification: No
Quality management systems (QMS): Yes
CSA STAR certification: No
PCI certification: No
Other security certifications: Yes
Any other security certifications: ISO 22301 Business Continuity Management System

ISO 27701 Privacy Information Management System

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

Request an accessible format

Cookies on Digital Marketplace

DXC Technology - Managed Container Services

Features

Benefits

Pricing

Service documents

Framework

Service ID

Contact

About your service

Service scope

User support

Onboarding and offboarding

Using the service

Scaling

Analytics

Resellers

Staff security

Asset protection

Backup and recovery

Data-in-transit protection

Availability and resilience

Identity and authentication

Audit information for users

Security governance

Operational security

Secure development

Separation between users

Energy efficiency

Pricing

Discount

Formula for calculating price of your services

Mandatory certifications

Cyber Essentials

Non-mandatory Standards and certifications

Social value

Service documents