Public Cloud Services Compute
Unleash the power of Azure Cloud with Viatel Technology Group. Migrate securely and optimise costs with a bespoke Azure solution and experience seamless migration, unmatched scalability, and innovation with Microsoft Azure. Benefit from expert guidance, comprehensive support, and tailored solutions designed to meet your unique business needs and drive success.
Features
- On-demand creation and management of virtual configurable servers
- Ability to scale compute resources up or down automatically
- Billing is based on usage (compute hours, storage, networking).
- Multiple Operating System Support
- Built-in redundancy, availability zones, and automated failover options.
- API and Automation Support
Benefits
- Reduced Capital Expenditure
- Faster Deployment
- Operational Flexibility
- Improved Reliability
- Deploy workloads in multiple geographic regions for lower latency
- IT teams do less managing infrastructure and more innovation.
Pricing
- Education pricing available
- Free trial available
Service documents
Request an accessible format
Framework
G-Cloud 15
Service ID
1 3 2 5 6 1 0 9 3 8 9 3 9 3 4
Contact
VIATEL TECHNOLOGY UK LTD
Gerard McCann
Telephone: +447590689465
Email: gerard.mccann@viatel.com
About your service
- Service categories
-
IaaS
IaaS Compute
- Bare metal
- Container and serverless engine compute
- Arm-based instances
- Other non-x86 instances
Virtualised x86
- General purpose
- Compute optimised
- Memory optimised
Accelerated
- GPUs
- APUs
Service scope
- Service constraints
- Viatel are happy to discuss your requirements in detail and provide information on any service constraints that might be relevant. Azure service constraints are the built-in limits, boundaries, and conditions that define how Azure services can be used, configured, and scaled. They exist to ensure platform stability, performance, security, and fair use across Microsoft’s global cloud infrastructure.
- System requirements
-
- Azure Account & Subscription
- A modern web browser with JavaScript enabled.
- Local tool requirements vary by OS and tool
- Azure supports a wide range of VM sizes
- For on-premises Azure integration hardware has specific requirements
- Microsoft Entra ID & Appropriate RBAC roles
- Internet connectivity to Azure endpoints
- OS that supports chosen tools
- Cloud deployment model
-
- Public cloud
- Private cloud
- Hybrid cloud
User support
- Email or online ticketing support
- Yes
- Support response times
- 24/7/365 support via NOC
- User can manage status and priority of support tickets
- Yes
- Online ticketing support accessibility
- None or don’t know
- 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 level details can be customised for customers to suit their needs.
Costs are provided according to requirements.
A technical account manager or cloud support engineer can be provided. - Support available to third parties
- Yes
Onboarding and offboarding
- Getting started
-
Full onboarding services are provided for all our services including managed services.
Azure onboarding typically begins with setting up the right foundation for your organization. An Azure account is created using a Microsoft Entra ID (formerly Azure Active Directory). This establishes identity management and allows control of user access, roles, and permissions.
Next, governance structure is defined. Management groups, subscriptions, and resource groups are created to organize resources logically. Role-based access control (RBAC), naming conventions, and tagging standards are applied early to ensure security, cost control, and scalability. Azure Policy and cost management tools are enabled to help enforce compliance and monitor spending from day one.
Once governance is in place, core services such as networking, storage, and security are configured. Virtual networks, subnets, and network security groups are set up, and Microsoft Defender for Cloud is enabled to improve the customer security posture. Customers can then begin deploying workloads using the Azure Portal, Azure CLI, or Infrastructure as Code tools like Bicep or Terraform.
To get started efficiently we follow Microsoft’s Cloud Adoption Framework, which provides best practices, reference architectures, and step-by-step guidance. Azure Monitor and Application Insights are used to track performance and reliability as you scale. - Service documentation
- Yes
- Documentation formats
- HTML
- End-of-contract data extraction
-
At the end of an Azure contract, users remain responsible for extracting and retaining their data before services are decommissioned. Microsoft provides multiple tools and export options to support secure and complete data extraction. The process typically begins by identifying all active resources—such as virtual machines, databases, storage accounts, and backups—within the Azure subscription using the Azure Portal or Azure Resource Graph.
Data can be extracted using native Azure services. For storage accounts, users can download blobs, files, and tables via the Azure Portal, Azure Storage Explorer, or Azure CLI. Databases such as Azure SQL Database, Cosmos DB, and managed instances support data export through built-in export features, backups, or tools like SQL Server Management Studio and Data Factory. Virtual machine data can be preserved by exporting disks as VHD files or creating final backups using Azure Backup.
Before contract termination, users should also export configuration data, logs, and monitoring information from Azure Monitor and Log Analytics. Once extraction is complete, data should be validated, securely transferred to an alternative environment, and stored in compliance with retention and regulatory requirements. After the contract ends, Microsoft deletes customer data according to its data retention and destruction policies, making timely extraction essential. - End-of-contract process
-
Full handover support is provided as part of our exit management. Viatel’s handover process is a structured transition that ensures continuity, security, and full transfer of operational responsibility from one provider to another or back to the customer. The process begins with planning and discovery, where Viatel documents the current Azure environment, including subscriptions, tenants, resource groups, networking, security controls, and deployed workloads. An asset inventory, architecture diagrams, and dependency maps are shared with the incoming party.
Next, access and identity are reviewed. Ownership of the Microsoft Entra ID tenant and Azure subscriptions is confirmed, and privileged roles are transferred. The incoming MSP is granted appropriate role-based access control (RBAC), while Viatel’s accounts are prepared for removal. Service principals, automation accounts, and managed identities are reviewed to avoid disruption.
Operational knowledge transfer follows, covering monitoring, backup and disaster recovery, patching, incident response, and cost management. Runbooks, Infrastructure as Code repositories, and configuration standards are handed over and validated. Open issues, risks, and upcoming changes are clearly documented.
Finally, a controlled transition period is completed, during which responsibilities are gradually shifted. Once accepted, Viatel’s access is revoked, credentials are rotated, and the handover is formally signed off. - Documentation accessibility standard
- None or don’t know
- How the documentation is accessible
-
Azure onboarding and offboarding documentation is designed to be easily accessible, centralized, and consistently maintained to support both technical and non-technical users. Most organizations store this documentation in a shared knowledge repository such as Microsoft SharePoint, Confluence, or an internal wiki, ensuring it is available to all relevant stakeholders. Access is typically managed through Microsoft Entra ID, allowing permissions to be aligned with user roles and ensuring sensitive information is protected.
Documentation is commonly linked directly from operational tools such as the Azure Portal, Microsoft Teams channels, or service management platforms. This makes it easy for users to find onboarding steps, approval processes, and offboarding checklists at the point of need. Clear version control and ownership are defined so updates reflect changes in security policies, governance standards, or platform architecture.
For accessibility and usability, the documentation is structured into clear sections with step-by-step instructions, diagrams, and links to official Microsoft guidance. Search functionality, tagging, and standardized templates help users quickly locate relevant content. Offboarding documentation is equally visible and integrated into identity and access management workflows, ensuring timely removal of access and resources. Together, this approach ensures Azure onboarding and offboarding documentation is discoverable, secure, and easy to follow.
Using the service
- Web browser interface
- Yes
- Using the web interface
-
Create and manage Azure resources
Users can deploy and manage virtual machines, storage accounts, databases, networks, web apps, and other Azure services.
Monitor resources and performance
View dashboards, metrics, logs, alerts, and health status of Azure resources in real time.
Configure security and access
Manage users, groups, roles (RBAC), policies, and identities through Microsoft Entra ID.
Manage subscriptions and billing
View costs, budgets, usage reports, invoices, and subscription details.
Use built-in tools and Cloud Shell
Access Azure Cloud Shell directly in the browser to run Azure CLI or PowerShell without local installation.
Deploy solutions using templates and wizards
Use guided setup wizards, ARM templates, and Marketplace offerings to deploy solutions quickly.
Limitations
Perform complex or large-scale automation efficiently
While possible, large automation tasks are better suited for scripts, CLI, PowerShell, or Infrastructure-as-Code tools.
Work fully offline - requires an active internet connection; offline management unsupported.
Customize low-level physical infrastructure
Users cannot access or control underlying physical servers, hardware, or Azure data center operations.
Run all advanced configurations comfortably
Some advanced or repetitive configurations are more practical via command-line tools or APIs than the web UI.
Bypass RBAC- users cannot perform tasks outside their RBAC roles.
Manage external, non-Azure infrastructure directly - Web interface accessibility standard
- None or don’t know
- How the web interface is accessible
-
The Azure Portal is designed to be accessible to users with a wide range of abilities by following recognised accessibility standards and inclusive design principles. It supports keyboard navigation, allowing users to move through menus, forms, and controls without relying on a mouse. This is particularly important for users with motor impairments. The portal also works with screen readers, using clear labels, semantic headings, and ARIA attributes so that users who are blind or have low vision can understand and interact with content effectively.
Colour contrast and text readability are carefully considered to support users with visual impairments or colour blindness. The interface allows browser-based zoom and text resizing without breaking layouts or losing functionality. Error messages and notifications are written clearly and are programmatically associated with relevant fields, helping users understand and correct issues.
Azure Portal aligns with widely recognised standards such as WCAG 2.1 Level AA, Section 508, and EN 301 549, which guide accessible web design. Microsoft also regularly tests the portal using automated tools and real-world assistive technologies to identify and fix accessibility issues. These features ensure that it is usable, understandable, and robust for users with diverse accessibility needs, enabling equitable access.. - Web interface accessibility testing
- Microsoft tests the Azure Portal’s web interface using a combination of automated tools, manual reviews, and real-world testing with assistive technologies. This includes validating the portal with screen readers, keyboard-only navigation, and other accessibility tools to ensure correct labels, focus order, and usability. Accessibility testing is aligned with standards such as WCAG 2.1 AA, Section 508, and EN 301 549. Microsoft also involves people with disabilities in functional testing as part of its accessibility validation process. The results of this testing are documented in Accessibility Conformance Reports, which help identify issues and guide ongoing improvements.
- API
- Yes
- What users can and can't do using the API
-
Azure provides comprehensive APIs that allow users to manage and interact with cloud resources programmatically. Using the Azure Resource Manager (ARM) and service-specific APIs, users can create, configure, update, and delete Azure resources such as virtual machines, storage accounts, networks, databases, and web applications. The APIs enable large-scale automation, repeatable deployments, and integration with DevOps pipelines and third-party tools. Users can monitor resources, retrieve logs and metrics, manage identities and access through Microsoft Entra ID, and control costs by querying usage and billing data. APIs also support Infrastructure as Code, allowing environments to be versioned and deployed consistently across regions.
However, there are limits to what users can do through the APIs. Users cannot access or control Azure’s underlying physical infrastructure, such as data centre hardware, networking equipment, or cooling systems. All actions are restricted by role-based access control, meaning users cannot perform operations beyond their assigned permissions. The APIs cannot be used offline and require authentication and network connectivity. Additionally, some portal-only guided experiences and previews may not be immediately available via APIs. Despite these limits, Azure APIs provide powerful, secure, and scalable control over cloud resources while abstracting away physical infrastructure management. - API automation tools
-
- Ansible
- Chef
- SaltStack
- Terraform
- Puppet
- Other
- Other API automation tools
- PowerShell DSC, Bicep, and custom scripts can also interact
- API documentation
- Yes
- API documentation formats
-
- Open API (also known as Swagger)
- HTML
- Command line interface
- Yes
- Command line interface compatibility
-
- Linux or Unix
- Windows
- MacOS
- Using the command line interface
-
The Azure CLI allows users to manage and interact with Azure resources programmatically from a terminal. Using the CLI, users can create, configure, and delete virtual machines, storage accounts, databases, networks, web apps, and other Azure services. It supports scripting and automation, making it ideal for repeatable deployments, DevOps pipelines, and infrastructure-as-code workflows. Users can also query resource status, monitor metrics, retrieve logs, manage identities through Microsoft Entra ID, and control costs by accessing usage and billing data. The CLI can be used locally on Windows, macOS, or Linux, or through the browser-based Cloud Shell, providing flexibility for remote administration.
Users cannot access or control underlying physical infrastructure, such as data center servers, networking equipment, or storage hardware. Actions are constrained by role-based access control (RBAC), so operations outside the assigned permissions are blocked. Some advanced or preview features available in the Azure Portal may not yet be fully supported in the CLI. The CLI also requires an active internet connection and authenticated access; offline usage is not possible. Despite these constraints, the Azure CLI provides powerful, scriptable, and secure control over cloud resources, enabling efficient management and automation without needing to rely on the web portal.
Scaling
- Independence of resources
- Scoped and planned for according to requirements.
- Usage notifications
- Yes
- Usage reporting
- 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
-
- Real-time dashboards
- Regular reports
- Reports on request
- Resource tagging
- Yes
- FOCUS resource tagging
- Yes
Resellers
- Supplier type
- Reseller providing extra support
- Organisation whose services are being resold
- Microsoft
Staff security
- Staff security clearance
- Other security clearance
- Government security clearance
- Security Clearance (SC)
Asset protection
- Knowledge of data storage and processing locations
- Yes
- Data storage and processing locations
- European Economic Area (EEA)
- 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
- In-house
- Protecting data at rest
-
- Physical access control, complying with another standard
- Encryption of all physical media
- Scale, obfuscating techniques, or data storage sharding
- Other
- Other data at rest protection approach
- All data is protected in line with ISO27001:2022
- Data sanitisation process
- Yes
- Equipment disposal approach
- A third-party destruction service
- Data sanitisation type
-
- Deleted data can’t be directly accessed / Cryptographic Erasure
- Physical Destruction / Hardware containing data is completely destroyed
Backup and recovery
- What’s backed up
- Scoped according to requirements.
- Backup controls
- In Azure, users control backups through Azure Backup and service-specific backup features. Backups are only performed for resources explicitly selected by the user, such as virtual machines, databases, or storage services. Backup policies define the schedule, frequency, and retention period, allowing different settings for different workloads. Some services, like Azure SQL Database and Cosmos DB, use built-in automated backups with configurable retention. Users can also choose which disks or data are included in backups. Role-based access control (RBAC) limits who can manage backup settings, while monitoring and audit logs help verify that backups run as intended.
- Datacentre setup
- Multiple datacentres with disaster recovery
- Scheduling backups
- Users schedule backups through a web interface
- Backup recovery
-
- Users can recover backups themselves, for example through a web interface
- 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
- Data protection within supplier network
- TLS (version 1.2 or above)
Availability and resilience
- Guaranteed availability
- Availability is provided according to services level purchased.
- Approach to resilience
- Resilience is in line with ISO27001:2022
- Outage reporting
- Email or phonecall
Identity and authentication
- User authentication needed
- Yes
- User authentication
- Multi-Factor Authentication (MFA)
- Access restrictions in management interfaces and support channels
- Access restriction processes are in line with ISO27001:2022
- Access restriction testing frequency
- At least every 6 months
- Management access authentication
-
- Multi-Factor Authentication (MFA)
- Username or password
- Devices users manage the service through
- Directly from any device which may also be used for normal business (for example web browsing or viewing external email)
Audit information for users
- Access to user activity audit information
- You control when users can access audit information
- How long user audit data is stored for
- User-defined
- Access to supplier activity audit information
- You control when users can access 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
- ISO/IEC 27001
- Information security policies and processes
- ISO27001:2022
Operational security
- Configuration and change management standard
- Supplier-defined controls
- Configuration and change management approach
- Our configuration and change management processes are in line with ISO27001:2022
- Vulnerability management type
- Supplier-defined controls
- Vulnerability management approach
- Vulnerability management processes are in line with ISO27001:2022
- Protective monitoring type
- Supplier-defined controls
- Protective monitoring approach
- Our proactive monitoring approach is in line with industry best practices and ISO27001:2022
- Incident management type
- Supplier-defined controls
- Incident management approach
- Our incident management approach is in line with industry best practices and ISO27001:2022
- Post-quantum cryptography secure
- Yes
Secure development
- Approach to secure software development best practice
- Supplier-defined process
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
- Unrivalled security on multiple levels – cloud, network and software. For dedicated storage, we guarantee that only your data is on the disc, and can identify the exact disc your data is on. Our solution also provides encryption, VPN connectivity and ensures that your data never leaves our network.
Energy efficiency
- Energy-efficient datacentres
- Yes
- Description of energy efficient datacentres
- Data centres are powered using 100% renewable energy
Pricing
- Discount for educational organisations
- Yes
- Free trial available
- Yes
- Description of free trial
- Yes, typically for 30 days. New users receive $200 USD in Azure credits to spend on any Azure service. A valid Microsoft account is needed. The trial allows users to provision virtual machines, storage accounts, databases, networking services, and more, giving a full preview of Azure’s cloud capabilities.
Discount
- Provide your minimum discount applicable to your baseline prices
- 1%
Formula for calculating price of your services
- Formula for calculating price of your services
-
Which of the core deployment models you intend to offer
Public CloudPublic 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
- Baseline prices are available on vendor websites.
- Baseline Pricing - Web link
- https://azure.microsoft.com/en-gb/pricing/calculator/
- -
- Minimum Discounting
- 1%
- +
- Onboarding Activity
- Onboarding costs may vary based on your specific requirements, please confirm with suppliers during the clarification process
- +
- Additional sources of cost
-
Cloud service costs direct service usage, consumption-based fees, and several indirect or hidden expenses. Infrastructure as a Service (IaaS) primarily charges for compute resources such as virtual machines, based on CPU, RAM, operating system type, and usage options like on demand or reserved instances. Storage costs vary depending on whether block, object, or backup storage is used, and on the level of redundancy required. Network and data transfer fees apply, especially for outbound traffic or cross region transfers. Additional expenses include software licensing, support tiers, monitoring and automation tools, and optional security features such as firewalls or compliance reporting.
Platform as a Service (PaaS) shifts focus to managed application environments. Costs include platform subscription fees for hosting, databases, and APIs, often charged per instance or compute hour. Managed database consumption contributes additional cost based on capacity, transactions, and resilience. Development tools, middleware, and API gateways may incur extra charges, while auto-scaling and premium performance tiers add further expense. Optional support, training, and third party integrations also influence total cost.
Both models include indirect costs such as data egress fees, migration work, vendor lock in, compliance audits, and potential downtime.
Costs may increase in line with currency fluctuations. - -
- Additional sources of cost reduction
- Multi year commitments on resources.
Mandatory certifications
- Mandatory certifications
-
Are you are bidding to offer IaaS and/or PaaS as a reseller or are you in sole control of the infrastructure
ResellerCloud service suppliers you intend to resell with evidence
Organisation 1
Organisation name
MicrosoftWebsite address/upload for organisation
UploadUpload
ProvidedISO 9001 certification
ProvidedISO 27001 certification
ProvidedISO 20000-1 certification
ProvidedAre you reliant on the Cloud Service Provider for some accreditations
Yes
Cyber Essentials
- Do you have a Cyber Essentials Plus certificate?
- Yes
- Cyber Essentials Plus certificate Number
- 83fce0e7-79db-4d46-8938-5ff749cb9a51
Non-mandatory Standards and certifications
- ISO 28000:2022 certification
- No
- Quality management systems (QMS)
- Yes
- CSA STAR certification
- No
- PCI certification
- Yes
- Who accredited the PCI DSS certification
- Kyte Global
- PCI DSS accreditation date
- Monday 3 March 2025
- What the PCI DSS doesn’t cover
- The scope is for our Blanchardstown data centre for physical security (clauses 9 & 12 in the PCI standard).
- Other security certifications
- Yes
- Any other security certifications
-
- ISO27001:2022
- Microsoft Solutions Partner for Security
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
- 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
- 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
- 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
- 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
-
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.
- 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
-
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
- Activities that demonstrate a collaborative way to work with a diverse range of businesses as part of the supply chain
- Plans for positive actions with community groups.
- Plans to respond flexibly and adapt approaches to community engagement and initiatives
-
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
- 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
-
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
- 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
- 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
- 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
-
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.
- Other measures to offer development opportunities for the target cohort(s) in the contract workforce
- Understanding of issues relating to entering the contract workforce
-
Mission: Build an NHS fit for the future: That is there when people need it; with fewer lives lost to the biggest killers; in a fairer Britain, where everyone lives well for longer.
Policy Outcome 8: Increasing productivity through physical and mental wellbeing: In the supply chain and communities in the relevant area.
- Understanding of issues relating to health and wellbeing, including physical and mental health, in the contract workforce
- 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
-