FC-0 — Physical & Virtual Substrate

Hardware lifecycle management · score 3, gap structural, DAPM Ceded The Dell Automation Platform provides full hardware lifecycle management for its supported substrate, and the substrate is Dell's own. Day 0 zero-touch device onboarding, Day 1 configuration automation that Dell states automates more than 400 manual steps, about 90 percent fewer than manual deployment (vendor-published figures, not tested by this assessment), and Day 2 full-stack validated updates — firmware, BIOS, and cloud stack software sequenced in one tested bundle with health-check gates, drift detection, zero-day patching, and certificate management. Cluster expansion, node removal, and resets are blueprint operations. Because Dell manufactures the hardware and authors the automation, firmware content is Dell-validated end to end: the enterprise consumes tested update bundles rather than assembling per-component firmware baselines. One precision matters: the surface unity here is hardware-plus-stack lifecycle, not hardware-plus-workload management — the Automation Platform has no workload management surface, and day-to-day workload operations live in the deployed stack's console. During lifecycle events the platform provides what Dell describes as graceful workload moves with automated node and cluster shutdowns, coordinated with the deployed stack. The gap from 4 is structural and two-fold: lifecycle operations are operator-initiated blueprint executions from the Dell portal rather than invisible platform behavior, and fully workload-transparent maintenance would require cooperation from a scheduler Dell does not own.

Substrate heterogeneity · score 1, gap structural, DAPM Ceded The Dell Automation Platform provides lifecycle automation for supported, validated Dell Private Cloud environments built on Dell PowerEdge servers and Dell storage. The offering is a validated, Dell-supported private cloud scope rather than a general-purpose control plane for heterogeneous third-party hardware estates — an enterprise with mixed OEM hardware cannot bring that estate under this control plane, and that is the product's premise rather than a maturity gap. Accelerator breadth exists in the PowerEdge portfolio across GPU vendors, but hardware management remains Dell-tooling-specific, and the depth of GPU-node coverage under Private Cloud blueprints specifically is thinner in public documentation than the general-purpose cluster story (an inference flagged rather than a confirmed limit; it does not affect this score). Score 1 reflects the single-OEM gradient band: unified management of one vendor's hardware family is operational coherence, not heterogeneity. Structural — deliberate design scope.

Substrate portability · score 1, gap structural, DAPM Ceded Dell Private Cloud exists where Dell racks exist. A public cloud deployment target for the Automation Platform's control plane is not described in Dell materials — the platform's portal can run online or on-premises, but what it manages is supported Dell infrastructure in customer-managed environments. Edge is the honest nuance: Dell Distributed Private Cloud addresses edge and distributed use cases as a distinct offering under the same Automation Platform family, so the platform family demonstrably reaches edge without the assessed offering itself stretching there unchanged. Score 1 reflects on-premises-only substrate scope for the assessed product, a notch above substrate-specific confinement because the platform extends to edge through a sibling offering, and below the band requiring a cloud offering of the control plane, which does not exist in any form. Structural — the product is inseparable from Dell-owned physical infrastructure.

FC-1 — Distributed Data & Context Fabric

Data location and gravity awareness · score 2, gap closeable, DAPM Retained Dell Private Cloud provides infrastructure-tier visibility through its unified portal — global asset inventory, hardware and cloud-stack state, capacity and health views, blueprint-validated configuration state — and through Dell AIOps, in-boundary via its documented Automation Platform integration, which adds cloud-based predictive telemetry with REST and webhook egress over the Dell estate. That is genuine programmatic infrastructure telemetry, and it is the boundary. No enterprise data catalog exists on this platform: nothing answers where data lives with residency or regulatory context, and nothing consumes location metadata for workload placement. A compliance query asking whether regulated data sits on compliant substrate cannot be answered from this control plane. Score 2 reflects the infrastructure-telemetry band: real visibility into substrate and stack, no data awareness above it. Closeable — a placement-consumable enterprise data catalog requires a new acquisition and integration the enterprise owns.

Governance and compliance metadata · score 1, gap closeable, DAPM Retained The platform's governance surfaces govern infrastructure, not data. Blueprint-driven validated-state monitoring, security configuration guidance, certificate management, and role-based access control over operations are documented for supported environments, and Dell storage carries retention and immutability controls — storage compliance features, not classification metadata. Enterprise-wide classification, regulatory tagging, and policy propagation across enforcement points are not described in the assessed offering's documentation — the governance story is stronger for access and protection controls than for estate-wide metadata classification and enforcement. Score 1 reflects access and protection controls without a classification or propagation capability. Closeable — estate-wide data governance requires acquiring a data governance platform (Collibra, Informatica, or equivalent) and integrating it against both this platform and the deployed stack.

Retrieval and context services · score 0, gap closeable, DAPM Retained Within the assessed boundary, no retrieval, semantic search, vector search, or managed RAG capability exists — Dell Private Cloud materials describe validated deployment and lifecycle management for supported cloud stacks, not data services. Dell sells a purpose-built retrieval and search stack in the Dell AI Data Platform, and in its written review of this assessment Dell stated that the AI Data Platform is a separate platform offering that should not be considered part of Dell Private Cloud. The instrument honors the vendor's own boundary: the capability exists at Dell, on a contract this offering does not include. Closeable — the closure path is the Dell AI Data Platform, a separate Dell platform acquisition with its own deployment and operating model, or a third-party retrieval stack the enterprise assembles. Retained by default — within this offering the enterprise owns the function entirely.

Data pipeline and lineage · score 0, gap closeable, DAPM Retained Within the assessed boundary, no data pipeline, change-data-capture, or lineage capability exists — Dell Private Cloud automates infrastructure and cloud-stack lifecycle, not data movement. Dell's pipeline and orchestration capability lives in the Data Orchestration Engine of the Dell AI Data Platform, which Dell's written review of this assessment places outside Dell Private Cloud as a separate platform offering. Closeable — the closure path is that separate Dell platform contract or a third-party integration acquisition; either way the enterprise signs an additional agreement and owns the integration surface. Retained by default — within this offering the enterprise owns the function entirely.

FC-2A — Infrastructure Orchestration

Workload universality · score 0, gap structural, DAPM Retained The Dell Automation Platform is not positioned as the workload scheduler for Dell Private Cloud. It deploys and lifecycles the cluster; what runs on that cluster — VMs, containers, databases, batch, AI — is orchestrated by the deployed cloud stack, under that vendor's control plane and that vendor's row on this instrument. A Dell scheduler, shared resource pools, cross-workload quota, and workload-level visibility are not described for the assessed offering. Dell materials do describe automated workload orchestration in Dell Distributed Private Cloud — a distinct offering outside this row's boundary — and workflow orchestration across infrastructure and applications in Dell Automation Studio, which Dell describes as CI/CD-native infrastructure orchestration; neither satisfies this function's test for the assessed control plane. Score 0 is the gradient reading against that test: the assessed control plane provides no workload-type orchestration of its own. This is the row's headline finding and it is a design decision, not a deficiency — Dell's architecture deliberately assigns workload orchestration to the stack the buyer chooses. The consequence is equally deliberate: the instrument's defining orchestration function arrives through a second vendor relationship, and the buyer owns the seam between the two planes. Structural.

Resource lifecycle automation · score 2, gap structural, DAPM Ceded Within fixed capacity, infrastructure lifecycle automation is the platform's core function: Day 0 cluster provisioning that Dell cites at roughly two and a half hours, automating what Dell states are more than 400 manual steps (vendor-published figures from Dell materials and a Dell-commissioned validation study, not tested by this assessment), blueprint-driven node expansion, removal, and reset, validated full-stack updates, and drift detection. The delivery-model anchor decides the score. On the lead go-to-market — Automation Platform subscription on customer-acquired Dell hardware, customer-operated through the portal, Dell handling Day 0 planning with optional managed services — scaling beyond owned capacity is procurement, and the control plane does not own the physical supply chain. That is the automated-lifecycle-within-fixed-capacity band: score 2. Dell APEX Infrastructure pay-per-use exists as a separately acquired consumption model in which Dell owns the hardware, meters usage, and pre-stages buffer capacity. Expandable capacity through a vendor-managed consumption model is outside what the assessed platform itself provides; the row scores the self-operated offering, and the consumption path is named as the buyer's separate acquisition. Structural — the physical supply-chain constraint applies to every on-premises platform sold as software on customer-owned hardware.

Policy and quota enforcement · score 1, gap structural, DAPM Ceded Dell's policy surface governs infrastructure configuration, not workloads. Blueprint-driven drift detection and compliance monitoring to maintain validated states, certificate management, and portal role-based access control over operations are documented and automated — the platform continuously checks that the infrastructure matches its validated definition, and the Technical Validation Report adds a governance nuance: deviation is itself a managed state, with controlled, documented version drifts available as an option for urgent updates and security patches. But the function asks for quotas, access, and constraints across workload types from a single surface, and Dell's surface covers no workload type: workload quotas, tenant access, and workload constraints live entirely in the deployed stack. Score 1 reflects genuine automated enforcement confined to the infrastructure-configuration domain. Structural — workload policy is the stack's domain by design. Ceded — the enforcement asset is the enterprise's accumulated blueprint and compliance configuration, held in Dell's proprietary formats with no open exit.

Substrate lifecycle integration · score 2, gap closeable, DAPM Ceded For planned lifecycle events, the integration is Dell's best story in this layer: validated full-stack updates sequence firmware and BIOS with cloud stack software with health checks, and Dell describes graceful workload moves with automated node and cluster shutdowns during maintenance. Dell's role centers on validated infrastructure and stack lifecycle operations, while workload behavior remains with the deployed stack. For unplanned events the integration is absent from Dell's surface: hardware failure to workload recovery is entirely the deployed stack's high-availability function, with Dell AIOps contributing detection and prediction telemetry but controlling nothing. The scheduling half of every integration here is executed by another vendor's control plane — Dell coordinates it during maintenance windows but does not own it, and no Dell path exists from a live hardware event to a workload scheduling action. Score 2: real maintenance-window integration, no event-time integration. Closeable — the missing wiring is enterprise-buildable: Dell AIOps exposes hardware health and prediction events through webhooks and REST, every supported stack exposes maintenance and HA APIs, and the enterprise that builds and maintains that bridge owns it.

Accelerator and GPU management · score 1, gap structural, DAPM Retained Dell emphasizes GPU-capable infrastructure — AI-optimized PowerEdge across accelerator vendors — and blueprint-driven deployment of supported environments in which AI workloads run. What is not described is a Dell-owned accelerator management control plane: accelerator-aware scheduling, multi-tenant GPU isolation, and GPU quota enforcement do not appear on any Dell surface in the reviewed materials. Those functions belong to the accelerator vendor's software layer and the deployed AI stack. Score 1 reflects hardware provision, lifecycle automation, and basic visibility without management capability. The depth of GPU-cluster blueprint coverage generally available in the Automation Platform catalog is thinner in public documentation than the general-purpose cluster story — flagged as the open evidence item for this cell; a platform-integrated GPU management capability, if documented, would move this to 2. Structural.

FC-2B — Execution & Runtime

Runtime universality · score 0, gap structural, DAPM Retained Dell ships no runtime. Every workload on a Dell Private Cloud — VM, container, database, batch job, AI inference — executes in the deployed cloud stack's runtime, under that vendor's execution surface, developer interface, and lifecycle model. Dell is not the workload runtime or developer execution surface; those functions remain with the deployed stack, and no Dell execution API, workload lifecycle operation, or developer surface is described. Score 0. Structural — runtime is the deployed stack's domain in Dell's architecture, and the enterprise's runtime experience is determined entirely by the second vendor relationship.

Persona abstraction at execution · score 1, gap structural, DAPM Ceded One leg of the persona triad exists. The operator persona is served: portal role-based access control over infrastructure operations, blueprint-gated change, portal and Dell AIOps substrate visibility, and audit of platform operations. But that is persona abstraction at the infrastructure tier: the operator persona is served there, while developer experience and execution-tier controls remain with the deployed stack. At the execution tier — developer intent declaration, operator override of running workloads, security audit of execution — no Dell primitives are described. The platform-gap versus opinion-gap distinction required at this cell is unambiguous: the execution-persona primitives are absent, not present-but-unconfigured. There is nothing to configure. Score 1 for the real operator and audit legs at the infrastructure tier. Structural.

Execution lifecycle and observability · score 2, gap structural, DAPM Ceded Two components are scored together at this function, and the score rests on one of them. Telemetry: real, and in-boundary — Dell AIOps, part of the offering through its documented Automation Platform integration (a boundary Dell confirmed in writing), provides cloud-based infrastructure observability with predictive analytics and health scoring across Dell compute, storage, and networking; the AIOps collector adds VM-level visibility correlated across host, switch, array, datastore, and virtual machine, pulled read-only through the virtualization layer's APIs; REST and webhook egress feed enterprise tooling. The portal's administration views add system, compliance, physical, updates, security, and support state. Execution lifecycle: absent by design — the platform manages no workload, and its workload telemetry is derivative, collected from the deployed stack's APIs rather than emitted by a runtime it operates. The wider AIOps family's application-observability and incident-correlation modules remain unconfirmed in current packaging and are not credited. Score 2: rich in-boundary infrastructure telemetry without execution-tier ownership or a shipped cross-workload correlation layer. Structural — the lifecycle half is a consequence of shipping no runtime; no acquisition closes it. Ceded — health scoring, prediction, and analytics intelligence are captive in Dell's SaaS with no open exit.

AI inference and agent execution · score 1, gap closeable, DAPM Retained Within the assessed boundary, no inference or agent execution capability exists as a service, and no validated serving component ships with the platform. Dell Private Cloud materials describe blueprint-driven deployment of supported environments in which AI workloads can run; the serving stack inside those environments is the enterprise's to acquire, deploy, and operate. Dell's curated AI component marketplace and its partner AI platform blueprints belong to Dell offerings the vendor's own review scopes outside this boundary. Score 1 is the enterprise-assembled band. A documented Dell Private Cloud blueprint that deploys a supported serving stack would argue the validated-path band; none appears in the assessed materials. Closeable — inference capability arrives with a partner AI subscription or a separate Dell platform contract. Retained by default within the offering.

FC-2C — The Reasoning Plane

Autonomous placement reasoning · score 0, gap structural, DAPM Retained Applying the integration-versus-coexistence test: Dell does not describe a Dell-owned placement or reasoning plane in this offering — there is no Dell component that derives placement by consuming live FC-1 metadata simultaneously with FC-2A state, because no Dell component performs placement at all. The Automation Platform deploys clusters and stops. Dell AIOps observes and predicts within the boundary but controls nothing, and the data-metadata ingredient of a reasoning plane exists at Dell only on a separate platform offering the vendor's own review places outside Dell Private Cloud. Dell itself declares the data-plane separation a reasoning plane would need bridged, and no component anywhere in the composition is a placement engine. Routing is not reasoning — and this platform does not even route. Applying the workload universality test: vacuously failed; there is no placement plane to evaluate for coverage. The concrete cross-constraint scenario, documented before locking: a new GDPR residency requirement arrives. Within the assessed boundary there is no Dell surface where the constraint can be expressed at all. Placement against the constraint happens in the deployed stack, where an operator hand-writes affinity rules, admission policies, or placement policies in another vendor's control plane. The Dell platform neither derives the placement nor executes a rule; it has no surface where the constraint could be expressed. The roadmap gate: the Automation Platform's announced agentic AI capabilities (later 2026 — generative interface, digital twin, collaborative agents) are infrastructure operations automation — deploy, monitor, manage — not placement reasoning, and vendor statements that private cloud tooling will reach this layer eventually are intention, not a product with a confirmed timeline. Structural.

FC-3 — Application Distribution and Governance

Application catalog and distribution · score 2, gap structural, DAPM Ceded Dell's blueprint catalog is a real catalog, not a bare deployment mechanism: Automation Platform blueprints are Dell-validated at publication, versioned, tested across supported hardware and stack combinations, and consumption is governed through portal access control. The catalog distributes infrastructure and cloud-stack outcomes consumed by operations teams rather than general application-tier artifacts. Against this function's test — a microservice, a traditional application, an AI agent, and an MCP server published and consumed through one governed catalog — application-tier distribution belongs to the deployed stack. Score 2 is the type-specific catalog band: genuine governance at publication and consumption, scoped to item types below the application tier. Structural — the catalog points down the stack by design. Ceded — accumulated catalog opinions live in Dell's proprietary blueprint format.

Application lifecycle governance · score 1, gap structural, DAPM Retained Application governance functions live in the deployed stack and the enterprise toolchain; Dell's described governance surfaces center on blueprint and marketplace items. What exists is blueprint and marketplace-item versioning with Dell-validated updates — the same infrastructure-lifecycle asset scored at FC-0 F1 and FC-2A F2, not application governance. Publication-to-retirement lifecycle, audit trails, and policy enforcement for applications live in the deployed stack and the enterprise's own toolchain. Score 1: version tracking of the platform's own units without application-tier enforcement. Structural. Retained by default — at the application tier Dell provides nothing, so the enterprise owns the function.

Developer experience and self-service · score 1, gap structural, DAPM Ceded Dell's self-service persona is the infrastructure operator, and for that persona the experience is real: blueprint-driven cluster and solution deployment from a portal, validated updates on demand. Dell's self-service experience is centered on the infrastructure operator persona; developer catalog discovery, configuration, and deployment self-service remains in the deployed stack — the same boundary that shaped FC-2B F2, appearing here at the catalog tier. Score 1: self-service for the wrong persona, none for the persona this function measures. Structural. Ceded — the operator self-service asset is portal-captive.

AI application and agent distribution · score 1, gap closeable, DAPM Retained Dell Private Cloud materials describe blueprint-driven deployment that includes AI workloads. Deployable is not catalog-governed: no AI application or agent distribution surface exists on this platform — no model version enforcement, no agent tool authorization, no prompt-injection controls, no output audit. The curated AI component marketplace Dell operates belongs to a separate Dell platform per the vendor's own review of this assessment. Score 1: AI workloads reach the platform through deployment automation, not through a governed distribution catalog. Closeable — AI distribution governance arrives with the deployed stack, a separate Dell platform, or a dedicated acquisition. Retained by default within the offering.

FC-4 — Integration Fabric

Event fabric and messaging · score 0, gap closeable, DAPM Retained Within the assessed Dell Private Cloud boundary, no messaging or eventing capability is described — no event bus, schema enforcement, fan-out, replay, or delivery guarantees as a service. The enterprise acquires and operates a messaging platform (Apache Kafka, a supported Kafka distribution, or equivalent) on the deployed stack. Closeable, and the closure deploys onto a hospitable composed estate — but it is a material platform acquisition with its own lifecycle burden, and every event-driven integration until then is a point-to-point connection the enterprise builds and maintains.

API management and gateway · score 0, gap closeable, DAPM Retained Dell materials document REST APIs and API-driven management and orchestration surfaces, but no dedicated API lifecycle or gateway capability is described in the assessed product set — no publication workflow, versioning governance, rate limiting, transformation layer, or API-level audit as a service. Closeable through acquiring an API management platform (Kong, 3scale, Apigee, or equivalent) operated on the deployed stack.

Workflow and process orchestration · score 0, gap closeable, DAPM Retained Dell has two workflow-shaped products and both fall outside this function. Dell Automation Studio (generally available June 2026) is what Dell describes as a CI/CD-native orchestration toolkit for full-stack automation across infrastructure and applications — IT operations automation, not business process orchestration; infrastructure pipeline automation does not satisfy a function defined by long-running transactions, saga and compensation patterns, and business processes. The Data Orchestration Engine orchestrates data pipelines, credited at FC-1 F4 — counting it again here would credit one asset at two functions. A unified business-process and AI-chain orchestration capability is not described in the assessed product set. Score 0. Closeable through acquiring workflow orchestration tooling for each workflow class.

SaaS and enterprise system integration · score 0, gap closeable, DAPM Retained Within the assessed boundary, no maintained connectors to enterprise systems of record are described — no SAP, Salesforce, ServiceNow, Workday, or mainframe integration as a managed service. Dell owned this function and sold it with the Boomi divestiture in 2021. What remains inside the boundary — the Data Analytics Engine's data-source connectors — federates queries for analytics; it is not system-of-record integration with transformation, lifecycle management, and lineage. This is the most operationally expensive function to own when absent: every system-of-record connection is a point-to-point integration the enterprise builds and maintains, with the full gap-lifecycle cost per connection. Closeable through acquiring an integration platform (Boomi, MuleSoft, a supported Camel distribution, or equivalent) — itself a material investment.

AI-native integration · score 0, gap closeable, DAPM Retained No Dell AI integration service is described in the reviewed materials: MCP tool connection management, agent-to-agent identity propagation, model API federation, and semantic routing do not appear in Dell's documented product set. What the materials do describe — an agentic AI layer that analyzes telemetry, understands natural-language requests, and designs and schedules maintenance — is AI applied to IT operations automation, a different function from AI integration fabric for customer applications; the distinction is load-bearing for this cell. The AI endpoints present on a Dell Private Cloud — NIM inference APIs, a partner agent platform's internal framework — are partner runtimes whose deployment is credited at FC-2B F4; deploying an AI component is not providing AI integration fabric. Score 0. Closeable through acquiring an AI gateway or MCP management capability as the category matures.