# Dell AI Factory with NVIDIA — 4+1 Layer AI Infrastructure Assessment

> Mapped to the 4+1 Layer AI Infrastructure Model  
> Version: v2.6 - Codified-Criteria Audit & Watch-List Roll · Date: July 12, 2026  
> Source: DTW 2026, GTC 2026, Dell press releases (March 16, May 18, June 22, 2026), Dell InfoHub documentation, Dell AI infrastructure product/marketing briefing (July 2026), published 4+1 model. v2.5 (briefing + DAPM axis reconciliation): DAPM re-reasoned from the customer's seat throughout — the rating measures the enterprise-to-vendor authority relationship; vendor-to-vendor framing (Dell-cedes-to-NVIDIA) retired to the nvidia[] dependency column and borrowedJudgment narrative. 2A Dell CSI Operator Ceded→Delegated (consumed interface is the multi-vendor CSI/K8s standard). GA-gate descores to dated watch-lists: 1A Exascale (targeted early 2H CY26, unconfirmed), 1C KV cache offload (NVIDIA CMX pre-GA), 2B Deskside Agentic AI (NemoClaw/OpenShell alpha). 1B GPU-accelerated DSE watch-listed: upstream Elasticsearch 9.4 took cuVS to GA April 2026, but upstream GA never moves an OEM cell — Dell-side GA unconfirmed in Dell docs. statusLabel convention ratified: capability vocabulary only; authority lives in the per-component DAPM chips. Summary rewritten: capture mechanism named (decoupled/invisible); 2C gap upgraded from instrument finding to vendor-confirmed deliberate ecosystem strategy. No layer status changed. v2.6 (July 12, 2026, codified-criteria audit): the canonical row re-read under the methodology's new capability grading criteria and channel-substitution rule. Trust3 Delegated→Ceded (proprietary governance platform; policies captive to the partner through any paper). 2B blueprint component re-reasoned to menu-altitude Delegated (deployed platforms capture per-choice, to the ISV). 1B held at moderate with the frontier check written in (rule 6: DSE is general but below the integrated-retrieval frontier, GPU path unconfirmed). Watch-lists rolled: Exascale still 2H 2026 (now expanding to 4-in-1 with PowerFlex, 1H 2027); GPU-accelerated DSE flagged as slipped — Dell's '1H 2026' passed without doc confirmation. No layer status changed.  
> Published by: The CTO Advisor LLC · thectoadvisor.com  
> Author: Keith Townsend

[Full interactive assessment](https://layer2c.com/assessment/dell) · [Methodology](https://layer2c.com/methodology) · [What Is Layer 2C?](https://layer2c.com/what-is-layer-2c)

## Executive Summary

Dell has one of the most credible on-prem AI Factory infrastructure stacks in the market. Its credibility comes from physical infrastructure (Layer 0), storage and data lifecycle integration (Layers 1A/1B/1C, where the Dataloop acquisition gives Dell its first proprietary software asset in the data lifecycle), and ecosystem packaging (Layer 3). From the buyer's seat, the authority profile is just as legible: the enterprise retains commodity compute, cedes its storage and pipeline opinions to Dell, and inherits NVIDIA's judgment for everything GPU-aware above the rack.

Dell's capture is decoupled and therefore mostly invisible. The data and table formats are genuinely open: Iceberg, Trino, S3-interface object storage. Schemas lift and catalogs swap. That openness is true and reassuring, and it's the layer Dell's own teams point to when they push back on authority scores. The captive layers sit above the data: the MetadataIQ catalog structure, Data Orchestration Engine pipeline logic, PowerRack integration, and Spectrum-X fabric opinions. The buyer feels portable because the bytes are portable. The opinions aren't.

Dell's owned capability above the rack is thin by design: validated ISV blueprints and human services at Layer 2B, chassis-level management at Layer 2A. GPU scheduling judgment is NVIDIA's regardless of whose paper the license rides on. The deskside agentic runtime is pre-GA and watch-listed, not scored.

The reasoning-plane gap is no longer just this instrument's finding; it's Dell's stated strategy. In a July 2026 briefing, Dell confirmed both halves of the boundary: the telemetry exists from Layer 0 up, and the decision layer is deliberately left to the ecosystem. 'I can give you the telemetry, but the ultimate decision comes down to somebody making the decision.' Security is not governance. Security constrains who can access the platform. Governance constrains what the platform does. The Dell AI Factory has security. It does not yet have governance at the infrastructure level.

That does not make the AI Factory weak. It exposes where the next control-plane battle will be fought.

## Layer Status

| Layer | Status | Classification |
|---|---|---|
| Layer 0 · Compute | ● Dell Strength | Compute & Network Fabric |
| Layer 1A · Storage | ● Dell Strength | Data Storage & Governance |
| Layer 1B · Retrieval | ◑ Elastic-Powered Retrieval | Context Management & Retrieval |
| Layer 1C · Pipelines | ◑ Dell + Dataloop | Data Movement & Pipelines |
| Layer 2A · Orchestration | ◑ Rack-Level Management | Infrastructure Orchestration |
| Layer 2B · Runtime | ◑ Blueprints + Services | Application Runtime & Execution |
| Layer 2C · Reasoning | ○ Enterprise Responsibility | Agentic Infrastructure — The Reasoning Plane |
| Layer 3 (+1) · Applications | ◇ Partner Ecosystem | AI Application Layer — The Value Plane |

## DAPM Profile

| Classification | Count | Meaning |
|---|---|---|
| Retained | 4 | Enterprise owns and controls this capability |
| Delegated | 11 | Provided by substitutable partner; enterprise retains swap authority |
| Ceded | 9 | Vendor controls this; enterprise has no governance authority |
| Absent | 0 | No capability at this layer |

## Strongest Layers

- **Layer 0** (Compute & Network Fabric) — Dell Strength
- **Layer 1A** (Data Storage & Governance) — Dell Strength

## Gap Areas

- **Layer 2C** (Agentic Infrastructure — The Reasoning Plane) — Enterprise Responsibility

## Layer-by-Layer Detail

### ● Layer 0 · Compute: Compute & Network Fabric

*Raw compute, networking, and acceleration fabric*  
**Status:** Dell Strength

**PowerRack** [DAPM: Ceded]  
Turnkey rack-scale: compute, networking, storage integrated with thermal/power management as one unit. Integrated-system rule: the buyer's rack-integration opinions cannot be lifted to another vendor as deployed.

**PowerEdge XE9812 (Vera Rubin NVL72)** [DAPM: Retained]  
10x lower cost-per-token than Blackwell for agentic inference. Commodity-substitutable server: NVL72 systems ship from multiple OEMs, so workloads move without rebuilding.

**Pro Max GB300 (Deskside)** [DAPM: Retained]  
120B–1T parameter models. MaxCool liquid cooling. ~3 month break-even vs cloud.

**PowerSwitch SN6000-series** [DAPM: Ceded]  
NVIDIA Spectrum-6 Ethernet. 800+ Tb/sec east-west. Networking opinions are embedded in the Dell/Spectrum-X stack with no abstraction layer offered that would make them portable to alternative switching infrastructure such as Juniper or Aruba.

**PowerCool CDU C7000** [DAPM: Retained]  
First rack-mount CDU for Vera Rubin NVL72 density. 4U, 19", up to 40°C facility water. Physical plant accumulates no portable opinions — no lock-in surface.

**Gap Analysis:** Dell retains platform packaging authority at Layer 0, but the accelerator fabric and high-performance AI networking roadmap are structurally tied to NVIDIA. Dell provides genuine engineering differentiators in thermal design, rack integration, and mechanical authority. The networking silicon dependency is worth tracking.

**Borrowed Judgment:** Structural co-dependency: Dell retains mechanical authority, NVIDIA retains silicon authority. If NVIDIA changes the Spectrum roadmap, Dell's PowerRack networking story changes with it. From the buyer's seat, the ratings are unaffected by which vendor holds the captive layer: PowerRack and PowerSwitch opinions can't leave regardless of whose silicon sits under the Dell brand.

### ● Layer 1A · Storage: Data Storage & Governance

*Durable, governed data foundation — the Governance Catalog that Layer 2C queries*  
**Status:** Dell Strength

**PowerScale (File Engine)** [DAPM: Ceded]  
MetadataIQ integration. NeMo Retriever connector. pNFS 25% throughput improvement. PowerScale storage opinions (configs, tiering policies, performance tuning) are captive to the Dell platform — the enterprise cannot lift them to Alletra or VAST without rebuilding.

**ObjectScale (Object Storage)** [DAPM: Delegated]  
S3-compatible. S3 over RDMA. NVIDIA Omniverse integration. Palantir Ontology deploys here. S3-compatible interface; object-storage opinions (buckets, lifecycle, policies) lift to any S3 platform. ObjectScale is a proprietary implementation behind the multi-vendor S3 standard — the consumed interface keeps object opinions portable, so Delegated (not an open substrate the enterprise operates, which would be Retained). The captive surface is MetadataIQ, not ObjectScale itself.

**MetadataIQ** [DAPM: Ceded]  
Indexes billions of files across PowerScale/ObjectScale. Foundation of the governance catalog. Metadata indexing opinions and catalog structure are captive to Dell.

**Trust3 AI Integration** [DAPM: Ceded]  
Storage-layer governance: sensitive data discovery, 'write once, apply everywhere' policy, AI auditing. EU AI Act/GDPR/HIPAA. Proprietary single-vendor governance platform on Dell paper — the 'write once, apply everywhere' policies are authored in Trust3's engine and do not lift to another governance ISV without rebuilding. Channel-substitution rule: Ceded to the chosen partner through any paper.

**Cyber Resilience (Built-in)** [DAPM: Ceded]  
Zero Trust, encryption, RBAC, immutable snapshots, XDR, data masking, air-gapped backup. Security implementation captive to Dell storage platforms — policies and configurations do not lift to another vendor's storage.

**Gap Analysis:** Dell's strongest layer after Layer 0. Trust3 AI provides agentic-AI-aware governance. The Exascale 3-in-1 architecture signals where the platform is heading on data locality, but it is watch-listed pending GA confirmation and not scored. The strategic question: is MetadataIQ metadata rich enough to drive Layer 2C placement decisions? Dell's marketing says yes. The proof is whether any Layer 2C can query it programmatically. The July 2026 briefing confirmed the telemetry and access-control surfaces exist; the reasoning consumer does not.

**Borrowed Judgment:** Low. Dell owns the storage platforms, metadata layer, and cyber resilience stack. NVIDIA provides acceleration, not governance logic. From the buyer's seat, the captive value is MetadataIQ: catalog structure and indexing opinions cannot leave the Dell platform. ObjectScale's S3 interface keeps object opinions portable to any S3 platform (Delegated — a proprietary implementation behind a multi-vendor standard, not an open substrate the enterprise operates); Trust3's governance policies are the partner's captive surface — Ceded to Trust3, not to Dell.

### ◑ Layer 1B · Retrieval: Context Management & Retrieval

*Low-latency retrieval for RAG — vector/hybrid search, context windows*  
**Status:** Elastic-Powered Retrieval

**Dell Data Search Engine (Elastic)** [DAPM: Delegated]  
Elasticsearch 9.4. Hybrid keyword+vector search. MetadataIQ integration. LangChain support. Available now on Dell paper; the GPU-accelerated path is watch-listed pending Dell doc confirmation. Elasticsearch opinions (indices, queries, pipelines) lift to any Elastic deployment.

**Incremental Indexing** [DAPM: Delegated]  
Only updated files re-indexed. Keeps retrieval synchronized with governance catalog.

**Analytics Engine Agentic Layer + MCP Server** [DAPM: Delegated]  
Unifies vector stores across Iceberg, Data Search Engine, PostgreSQL+PGVector. Agent-queryable through the open MCP interface.

**Gap Analysis:** Three-party dependency: Dell (storage + metadata), Elastic (search intelligence), NVIDIA (acceleration). STX is non-differentiating — every storage vendor has it. Dell's differentiation is MetadataIQ integration and the Elastic partnership, not NVIDIA acceleration.

Frontier check (capability rule 6, July 2026): the 1B frontier is now integrated AI-retrieval platforms delivered on vendor paper — VAST InsightEngine natively and through the Cisco and Supermicro channels (strong). Dell's DSE is a general-purpose search engine (rule 4 favors its generality — Elasticsearch runs retrieval workloads Dell never anticipated) that the customer assembles into RAG, with the GPU-accelerated path still unconfirmed on Dell paper. Real, deployable, general, but below the frontier and gated — moderate holds on rules 5 and 6.

**Borrowed Judgment:** Moderate, distributed across two partners. Search intelligence is Elastic's. Acceleration is NVIDIA's. Dell's durable value is the data substrate — if you swap search engines, PowerScale data doesn't move. From the buyer's seat the retrieval opinions themselves (Elasticsearch indices, queries, pipelines) lift to any Elastic deployment, which is what keeps the layer Delegated rather than Ceded.

### ◑ Layer 1C · Pipelines: Data Movement & Pipelines

*Move/transform data — ETL/ELT, lineage, cost-aware movement, KV cache tiering*  
**Status:** Dell + Dataloop

**Data Orchestration Engine (Dataloop)** [DAPM: Ceded]  
No-code/low-code AI data lifecycle. Dell's most meaningful software acquisition (~$120M, Dec 2025). GA confirmed: deployment documentation on Dell InfoHub and an orderable product page (verified July 2026). Proprietary pipeline orchestration — pipeline definitions built in the engine are captive to Dell.

**Orchestration Engine Marketplace** [DAPM: Delegated]  
200+ models, NVIDIA NIMs, Blueprints, AI-Q templates. Substitutable catalog content.

**Data Analytics Engine (Starburst)** [DAPM: Delegated]  
GPU-accelerated SQL. Agentic Layer + MCP Server for agent access. Trino/Iceberg substrate: schemas and materialized views lift to another engine, catalogs swap — the briefing's own portability argument is the Delegated rationale.

**Gap Analysis:** Dell's most significant strategic software move. Dataloop gives Dell proprietary orchestration logic — its first owned software asset in the data lifecycle. From the buyer's seat that ownership reads as decoupled capture: the data and table formats are open (Iceberg, Trino), so schemas lift and engines swap, while the pipeline opinions built in the no-code tooling are captive to Dell. The July 2026 briefing pushback made the instrument's case: open formats prove data portability, and data portability is the decoy — it says nothing about where orchestration authority accumulates.

**Borrowed Judgment:** From the buyer's seat: the enterprise inherits Dell's orchestration opinions outright at the engine (Ceded, first-party — Dell borrows little from partners there). Starburst-layer analytics judgment is swappable (Delegated). KV-cache judgment moved to the watch-list with the capability.

### ◑ Layer 2A · Orchestration: Infrastructure Orchestration

*GPU scheduling, quotas, RBAC, fair-share scheduling, utilization optimization*  
**Status:** Rack-Level Management

**Integrated Rack Controller** [DAPM: Ceded]  
Physical rack management — power, thermal, firmware, device inventory. Operates below Layer 2A. The buyer's rack-management opinions (power/thermal/firmware baselines) are captive to Dell PowerRack.

**OpenManage Enterprise** [DAPM: Ceded]  
Infrastructure lifecycle management. Manages the chassis, not GPU workloads. Fleet templates, policies, and baselines do not lift to another OEM's management plane.

**Dell CSI Operator** [DAPM: Delegated]  
Dell's one K8s operator — storage provisioning, not compute orchestration. The consumed interface is CSI/Kubernetes, a genuine multi-vendor standard: provisioning opinions live in Kubernetes-standard objects (StorageClasses, PVCs) and survive a swap to another vendor's CSI driver without rebuilding the layer.

**Gap Analysis:** Dell manages the rack. NVIDIA manages the GPU-aware substrate. That distinction matters because AI Factory differentiation depends less on whether the rack can be deployed and more on how scarce accelerated capacity is scheduled, partitioned, licensed, and governed at runtime. ClearML provides floating NVAIE license management — three authorities for one optimization function.

**Borrowed Judgment:** High. GPU-aware orchestration primitives are NVIDIA-controlled. Dell's authority is limited to physical chassis management (Layer 0), storage provisioning (Layer 1A), and deployment automation (Day 0/1). No alternative GPU scheduler exists within the Dell AI Factory. The July 2026 briefing confirmed the posture: Dell positions everything above the rack as ecosystem, not owned capability.

### ◑ Layer 2B · Runtime: Application Runtime & Execution

*Model serving, agent execution, inference APIs, distributed inference*  
**Status:** Blueprints + Services

**Agentic AI Platform (Blueprints)** [DAPM: Delegated]  
Cohere North, DataRobot, ClearML blueprints. Dell provides hardware substrate and services. Menu-altitude Delegated: the choice among validated ISV platforms is real before purchase. Once deployed, each chosen platform captures per its own terms — a production Cohere North estate's orchestration opinions are Ceded to Cohere through any paper, per the channel-substitution rule. Dell holds the menu, not the capture.

**Accelerator Services for Agentic AI** [DAPM: Retained]  
Dell's human-delivered value: strategy, deployment, optimization. Services, not software — expertise transfers to the customer, no captive opinion layer.

**Gap Analysis:** What ships on Dell paper at 2B is exactly what a customer can buy and keep or swap today: validated ISV agent platforms delivered as Dell blueprints, and Dell's human expertise to deploy them. Dell owns no runtime software — model serving, agent execution, guardrails, and distributed inference are NVIDIA or ISV capabilities, carried in the dependency column. The NVIDIA deskside agent runtime (NemoClaw/OpenShell) is alpha and watch-listed, consistent with its treatment on the NVIDIA row. Dynamo's KV-aware routing remains the closest thing to placement reasoning in the stack — single-variable cache-locality optimization, not multi-variable policy.

**Borrowed Judgment:** Total for the runtime the enterprise actually consumes: the NVIDIA path arrives with NVIDIA's judgment end to end — closed NIM serving decisions the enterprise can't inspect, Dynamo routing behavior, guardrail defaults. That judgment is inherited through the dependency column, not through a scored Dell component. Dell's owned contribution is curation and services; the blueprint menu keeps pre-purchase choice open (deployed platforms capture per-choice, to the ISV rather than to Dell), and Accelerator Services expertise transfers to the customer.

### ○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane

*Policy-driven placement and resource coordination — the Autonomy Layer*  
**Status:** Enterprise Responsibility

**Gap Analysis:** The 4+1 model defines Layer 2C as a required function of AI infrastructure — policy-driven decisions about where compute runs relative to data, which model serves which request, and how cost/compliance/latency are arbitrated in real time. Dell does not provide this function. The enterprise retains responsibility for it.

Applying the 'Routing Is Not Reasoning' test: AI-Q 2.0 = workflow scaffolding. OpenShell/NeMo Guardrails = constraint enforcement. Dynamo = performance routing. None provides multi-variable policy-driven placement.

The July 2026 briefing confirmed the gap in Dell's own words, twice. First, the telemetry-versus-decision boundary: Dell has telemetry from Layer 0 'all the way to 2B or even 2C,' token metrics per query, tools and guardrails — 'but the ultimate decision of what is economical or not comes down to somebody making the decision. I can give you the telemetry.' Dell provides the inputs to a reasoning plane and explicitly disclaims the decision layer. Second, the strategy: 2C and above is a deliberate ecosystem play — 'we designed the ecosystem program for 2C and 3 to give the flexibility and not try to be the winner of all, because we don't know who's going to win those layers.' The gap is a decision, not an omission. For the buyer that matters: bringing your own 2C (Kamiwaza, ClearML, potentially Palantir Ontology) collides with no Dell roadmap.

The enterprise must build custom 2C logic (6-12 months), bring a partner, or operate without it. Most will choose option 3 — the gap isn't visible until production agentic workloads expose it.

Dell + Intel 'actively addressing' an AI-factory control plane (SiliconANGLE, May 2026) remains security/governance framing with no product announced — still not scoreable.

**Borrowed Judgment:** There is no judgment to borrow — the enterprise retains full responsibility for this function. That responsibility is implicit: most enterprises operating Dell AI Factory infrastructure do not yet recognize Layer 2C as a distinct function they need to provide.

### ◇ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane

*AI-powered business capabilities — business logic, workflow automation*  
**Status:** Partner Ecosystem

**Dell AI Ecosystem Program** [DAPM: Delegated]  
Structured ISV validation path. Partners: Google, Hugging Face, OpenAI, Palantir, Reflection, ServiceNow, SpaceXAI. Substitutable partners on Dell paper.

**Dell Enterprise Hub (Hugging Face)** [DAPM: Delegated]  
Curated open-weight models on PowerEdge. DeepSeek, GLM, Kimi, Gemma, Nemotron, Mistral, Arcee. Model choices and fine-tunes are portable — open-weight substrate.

**Security Stack** [DAPM: Delegated]  
CrowdStrike + Fortanix + F5 + Intel confidential computing. Infrastructure security, not agent governance. Substitutable security ISVs — distinct from the Ceded cyber-resilience implementation built into Dell storage at 1A.

**Gap Analysis:** One of the strongest on-prem AI ecosystem stories in market. Each partner maps to a coherent use case. But each brings its own governance domain — Palantir Ontology governs within Palantir's domain, ServiceNow Otto within ServiceNow's. Nobody governs ACROSS domains on shared infrastructure. Security protects the platform from threats. Governance constrains what the platform does. Both are necessary. Only security is present.

**Borrowed Judgment:** Distributed across partners, which is architecturally correct at Layer 3. The structural problem: no cross-domain infrastructure judgment (Layer 2C) constrains all agents regardless of which ISV built them.

---
*Layer2C · AI Infrastructure Decision Intelligence · The CTO Advisor LLC · thectoadvisor.com*