NVIDIA Real Estate and Construction Global

Zaha Hadid Architects

Zaha Hadid Architects needed to shorten weeklong feedback cycles for highly detailed design scenes, protect a proprietary 40-year design archive, and scale AI-assisted visualization without sending sensitive client or intellectual-property data to external services.

40-year portfolio
over ten custom Omniverse extensions
reduced client feedback loops from one week to under 24 hours
scene datasets up to 60 million polygons

Reported impact

Business outcome

ZHA reduced client feedback loops from one week to under 24 hours, fine-tuned custom LoRAs and Stable Diffusion models on proprietary design data, and created an extensible Omniverse-based platform that reuses decades of portfolio content while keeping sensitive design data on premises.

  • Compliance
  • Productivity Improvement
  • Speed to Market

Solution

Zaha Hadid Architects built a local AI design pipeline around NVIDIA RTX 6000 Ada Generation GPUs, NVIDIA Omniverse, OpenUSD, and NVIDIA NIM large language models. High-end workstations with up to four GPUs handle rendering, simulation, model fine-tuning, and inference onsite so the firm can keep its 3D scenes, imagery, and client work local. ZHA combines Stable Diffusion, DALL-E 2, Rhino.ai, and custom LoRA workflows to turn parametric concepts into client-ready visuals faster, while NIM-backed tagging and search services organize its proprietary image archive for style transfer and geometry analysis. Through its CODE group, the firm also built more than ten Omniverse extensions and the ZSPACE Create interface so geometry processing, robotic simulation, environmental analysis, and rendering can share the same OpenUSD-based workflow instead of forcing teams to manually reformat scenes between tools.

Data flow

Design geometry and proprietary image assets stay on local RTX workstations, flow through OpenUSD into Omniverse, are tagged and searched by NIM-backed services, and are then combined with generative models such as Stable Diffusion and DALL-E 2 to produce client visuals and design-analysis outputs.

Solution architecture

8 components · 3 layers
  1. Compute
    • NVIDIA RTX 6000 Ada Generation GPUs Provide the local compute needed for rendering, simulation, model fine-tuning, and inference.
    • Stable Diffusion Generates and refines architectural visuals from abstract concepts.
    • DALL-E 2 Supports rapid ideation and image generation inside the design workflow.
    • Rhino.ai Connects parametric design strategies to AI-assisted visualization workflows.
  2. Serving
    • NVIDIA Omniverse Acts as the collaboration and workflow hub for ZHA's AI-augmented design stack.
    • NVIDIA NIM large language models Tag, search, and retrain models against ZHA's proprietary image archive.
    • ZSPACE Create Provides a unified interface for geometry, manufacturing, sustainability, and rendering tools.
  3. Orchestration
    • OpenUSD Carries live scene and asset data between design tools in the Omniverse pipeline.

Architecture clues

  • The AI workflow operates against over 40 years of proprietary models and imagery.
  • Workstations are equipped with up to four NVIDIA RTX 6000 Ada Generation GPUs.
  • ZHA built more than ten custom Omniverse extensions.

Evidence from the source

They have developed over ten custom Omniverse extensions integrated into its Spatial Technology Stack.
Workstations equipped with up to four NVIDIA RTX 6000 Ada Generation GPUs deliver a high-performance local compute environment.
ZHA manages an extensive, proprietary image database using NVIDIA NIM large language models to tag, search, and retrain models.
ZHA reduced client feedback loops from one week to under 24 hours using AI-assisted pipelines and Omniverse.
Transparency Evidence & methodology 85/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value85/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. NVIDIA

    Zaha Hadid Architects customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/zaha-hadid-architects-with-omniverse-and-usd/
    Source type
    Vendor-published customer story
    Published
    Jun 26, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Jun 26, 2026 · NVIDIA · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.