Parent folderOpen Confluence

RWS Architecture article

Virtual Desktop Infrastructure

Virtual Desktop Infrastructure is the product-neutral architecture building block for centrally managed virtual desktop access for user workloads. It states what DC 3.0 needs from

  1. Typeabb
  2. Statuscandidate
  3. Domainplatform
On this page
  1. ABB Virtual Desktop Infrastructure
  2. Summary
  3. Capabilities
  4. Constraints
  5. Service Description
  6. Roadmaps
  7. Landing Zones
  8. Interfaces
  9. Dependencies
  10. EIRA Alignment
  11. Available SBB's

ABB Virtual Desktop Infrastructure

Summary

Virtual Desktop Infrastructure is the product-neutral architecture building block for centrally managed virtual desktop access for user workloads. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides centrally managed virtual desktop access for user workloads.
  • Defines the functional, technical, security, and quality expectations that SBBs must satisfy.
  • Keeps service ownership, interfaces, and consumption boundaries visible before product selection.
  • Enables traceability from architecture intent to implementation, operational evidence, and consuming services.

Constraints

  • The resulting SBB must fit the end user productivity ownership model and document the support, lifecycle, and service-management boundary.
  • Security, privacy, logging, evidence, and compliance controls must be explicit enough to assess BIO2-aligned implementation where applicable.
  • Desktop environments must follow endpoint, identity, data-loss, and monitoring requirements.
  • SBBs must define user experience, persistence, support, and access boundaries.

Service Description

This ABB offers a VDI service that delivers governed desktop environments for users who need controlled access to DC 3.0 applications or administration paths. It is consumed by solution architects, platform teams, and service owners as the capability contract for selecting and shaping SBBs.

The service description remains implementation-neutral: product selection, hosting pattern, detailed runbooks, and service levels belong in the mapped SBB and related ADRs.

Roadmaps

  • Baseline: confirm scope, service ownership, constraints, and acceptance criteria for Virtual Desktop Infrastructure.
  • MVP: identify candidate SBBs and connect them to the service, support, and lifecycle model.
  • Next: add measurable service levels, evidence requirements, and roadmap dependencies once the SBB is selected.

Landing Zones

  • Private cloud landing zone in ODC-Amsterdam, following the RWS ICT Strategy 2025-2030 private-cloud direction.
  • Government cloud or external cloud landing zones only when the SBB documents the required control set, connectivity model, and data classification fit.

Interfaces

  • Remote display and broker protocols.
  • Identity, profile, storage, and endpoint-management integrations.
  • Monitoring and service-desk interfaces.

Dependencies

  • Depends on federated-authentication for a supporting capability or integration boundary.
  • Depends on smart-access for a supporting capability or integration boundary.
  • Depends on block-file-s3-storage for a supporting capability or integration boundary.
  • No implementing SBB is mapped yet; candidate SBB selection is a dependency for further elaboration.
  • Consuming ABB and SBB dependencies must be recorded as links when solution design identifies concrete upstream or downstream use.

EIRA Alignment

Available SBB's

  • No SBB is available yet. Candidate selection must be completed before this ABB can be promoted beyond capability intent.