Tag: enterprise AI adoption

  • Dell Shares AI Advances And New Metrics To Evaluate Infrastructure

    Dell Shares AI Advances And New Metrics To Evaluate Infrastructure

    At Dell Technologies World in Las Vegas, Dell Technologies chairman and CEO Michael Dell made a pointed argument to a room full of enterprise technology leaders: the metrics organizations use to evaluate infrastructure are evolving.

    GPU counts, cloud versus on-premises comparisons, and model benchmarks have dominated the conversation. Michael Dell’s day one keynote introduced two additional measures aimed at tying infrastructure decisions to actual outcomes: time to token, which measures how quickly a system processes a request and returns a usable AI output, and cost per token, which measures how cheaply that output is produced at scale.

    “Time to first token is incredibly important with investments of this scale,” Dell said on stage, noting that the company now has 5,000 enterprise customers running production AI workloads on its Dell AI Factory with NVIDIA platform. The figure represents a significant increase from the program’s launch two years ago.

    NVIDIA founder and CEO Jensen Huang, appearing alongside Dell, described why those metrics have taken on new urgency at both its NVIDIA GTC conference and at Dell Technologies World. Agentic AI systems, which reason, plan, and execute tasks autonomously over extended periods, require anywhere from 100 to 1,000 times more computation than a system simply responding to a query. “What took months now takes weeks, what took weeks now takes days, and what takes days now takes hours,” Huang said, describing the productivity transformation already underway at companies running agentic workflows. The demand implications for infrastructure are substantial.

    OpenAI president Greg Brockman echoed the framing independently on X.com the same day, writing that “tokens are rapidly becoming the universal input for solving problems.” The convergence of infrastructure vendors and model providers on the same metrics within weeks of each other signals a broader shift in how enterprise AI spending will be evaluated.

    The Data Problem Underneath the Infrastructure Problem

    One of Dell’s significant AI product announcements centered on a new data orchestration engine in the Dell AI Data Platform, which the company positioned as the missing layer between enterprise data and production-ready AI agents.

    The data orchestration engine is the platform’s intelligent control center. It indexes billions of unstructured files, builds governed data pipelines, and connects them to the models and agents that need them at speeds designed to make agentic workflows viable. Dell claims the updated platform delivers 12 times faster vector indexing, six times faster data querying, and 19 times faster time to first token compared to prior generations. While these claims still need to be validated, the proposed increase in performance is good news for enterprises looking to scale AI.

    The underlying problem the engine addresses is one most large organizations know well. Enterprises are simultaneously preparing existing data for AI use and reengineering the data infrastructure required to support AI workloads at scale. Those two efforts compete for the same resources and skills simultaneously.

    “If your data is siloed, your agents are blind,” Dell said. The statement is a precise description of why many enterprise AI pilots have not reached production. An agent operating without access to an organization’s proprietary data, internal knowledge bases, and operational systems cannot deliver the business context that makes agentic AI useful.

    Dell also announced GPU-accelerated SQL analytics through the Dell Data Analytics Engine, powered by Starburst, delivering up to six times faster query performance on NVIDIA Blackwell GPUs. Bank of America, which already has a partnership with Starburst, NVIDIA, and Dell, is among the institutions expected to use the capability.

    A Broad Ecosystem Built to Reduce Time to Production

    Dell announced a new Dell AI Ecosystem Program alongside a significant expansion of frontier model partnerships, positioning both as mechanisms for reducing the time between infrastructure procurement and production AI deployment.

    On the model side, Dell announced collaborations bringing several major AI providers on-premises to the Dell AI Factory. Google and Dell are collaborating to run Gemini 3 Flash models via Google Distributed Cloud on Dell PowerEdge XE9780 servers, enabling enterprises to run advanced generative AI workloads in a confidential computing environment that meets data residency and sovereignty requirements. OpenAI’s Codex will connect with the Dell AI Data Platform, giving enterprises a path to deploy agentic coding capabilities against their internal codebases, documentation, and business systems. SpaceXAI’s Grok is available in on-premises or hybrid enterprise deployments. Palantir’s Foundry and AIP platform is coming on-premises with its Ontology layer deployed on Dell ObjectScale and PowerFlex, allowing organizations to connect data sources and automate business workflows within their own environment.

    The Dell Enterprise Hub on Hugging Face gives enterprises on-premises access to a curated collection of open-weight models including MiniMax-M2.7, DeepSeek Pro, DeepSeek-V4, GLM 5.1, and Kimi K2.6, optimized for Dell AI Factory infrastructure.

    The Dell AI Ecosystem Program formalizes the partner relationship by providing software providers with a validated path to certify their solutions on Dell infrastructure. For enterprise buyers, the practical benefit is pre-validated deployment blueprints that automate the configuration of a specific software, service, or model, reducing integration work that has historically extended timelines from procurement to production.

    The Agent Harness: An Evaluation Criterion Enterprises Are Not Yet Asking About

    One of the more technically substantive moments in the keynote came from Huang’s description of how agents actually operate in production. Agents, he explained, do not run directly on the large language model. They run on a harness, a software layer that sits in a secure, governed sandbox. The harness manages the agent’s reasoning loop, controls tool access, determines when to call a large external model and when to use a smaller local model, and handles memory and context across multi-step tasks.

    NVIDIA’s OpenShell, the open-source sandbox, is now supported across the entire Dell AI Factory from deskside workstations through PowerEdge data center servers.  Dell also announced support for NVIDIA AIQ i.0 blueprints, which provide tested foundations for deploying multi-agent workflows.

    For CIOs evaluating AI infrastructure, the harness architecture is a meaningful addition to the evaluation checklist. Infrastructure that does not clearly define how agent harnesses are deployed, governed, and secured leaves a significant operational and security gap, particularly as agents acquire credentials, access enterprise systems, and take autonomous actions at machine speed.

    For example, “You can’t protect what you can’t see, and you can’t manage what you can’t see,” Dell said, framing the security challenge in terms that apply as directly to agents as to human users. An agent with compromised access or misconfigured permissions can propagate errors or security failures across workflows in ways that a single human user cannot.

    Hybrid AI Infrastructure and the Energy Constraint

    Dell’s survey data shows that 67% of AI workloads are already running outside the public cloud, and 88% of organizations are running at least one AI workload on-premises. The company positioned hybrid AI not as a transitional state but as the long-term architecture reality for most large enterprises.

    The new Dell PowerRack, announced Monday, is a fully integrated rack-scale system that combines compute, networking, and storage, engineered and validated as a single unit. It is designed to reduce the integration overhead of assembling AI infrastructure from components while supporting thermal management and power optimization at rack scale.

    Dell also introduced the Dell PowerCool CDU C7000, the first rack-mount cooling distribution unit designed to meet the cooling requirements of the NVIDIA Vera Rubin NVL72 platform, delivering more than 220 kilowatts of cooling capacity in a 4U form factor. A single rack of NVIDIA Rubin GPUs can draw over 130 kilowatts of power, and Dell noted that energy availability is an increasingly real constraint on AI deployment timelines, independent of sustainability considerations.

    For high-volume on-premises workloads, Dell introduced Dell Deskside Agentic AI, pairing high-performance Dell Pro Precision workstations with NVIDIA NemoClaw. The company claims the configuration enables enterprises to break even against public cloud API costs in as little as 3 months, converting variable token costs into a fixed infrastructure investment.

    What Changes for Enterprise Buyers

    The announcements from Dell Technologies World day one collectively continue to move the enterprise AI infrastructure conversation from capability to faster execution. The core questions are how quickly a given infrastructure configuration can reach first token on a production workload, at what cost per token, and with what governance architecture underpinning the agents running on it.

    The organizations best positioned to answer those questions are the ones that have already started rationalizing their data architecture, defined their hybrid workload placement strategy, and begun evaluating how agent harnesses will be secured and governed. The infrastructure improves almost daily, but the execution discipline required to use it remains the variable that separates AI programs that reach production from those that stay in pilot.

    Maribel Lopez is the founder and principal analyst at Lopez Research, a market research and strategy consulting firm specializing in enterprise AI, AI infrastructure, agentic systems, AI governance, and AI-driven customer experience. I version of this article of originally posted on Forbes.com.

  • Amazon Connect Is Now a Family of Products That Adds Agentic AI  to CX, HCM, Supply Chain and Healthcare

    Amazon Connect Is Now a Family of Products That Adds Agentic AI to CX, HCM, Supply Chain and Healthcare

    AWS is betting that Amazon Connect agentic AI belongs in supply chain, hiring, and healthcare — not just customer service. The branding is smart. Here’s my quick take. 

    For years, Amazon Connect meant one thing: contact center software. As of this week, it means four products, three new markets, and a bet that agentic AI is ready to run business operations — not just answer customer calls.

    At its “What’s Next with AWS” event, Amazon Web Services announced the expansion of the Amazon Connect name into a family of agentic business solutions. The original contact center product is now called Amazon Connect Customer. Three new products join it: Amazon Connect Decisions (supply chain and demand planning), Amazon Connect Talent (high-volume hiring), and Amazon Connect Health (clinical documentation and patient coordination). All four products sit under the Connect name. All four are agentic by design.

    The naming will raise eyebrows — more on that shortly. But the strategic logic is sound, and enterprise buyers should pay attention.

    What “Agentic by Design” Actually Means Here

    It’s worth being precise about what makes these products different from the AI-infused software most enterprises already live with.

    Agentic AI doesn’t just surface recommendations. It plans a sequence of actions, executes them, monitors the results, and adjusts. The word “connect” is doing double duty in this brand: it references both the product family name and the agents’ actual function — connecting to your systems, your data, and your workflows to get something done without waiting for a human to click “approve” at every step.

    The original Amazon Connect spent the last year being rebuilt on this principle. In 2025, AWS introduced what it called “next generation connect” — adding AI across the full customer journey, not just within a single interaction. Sentiment analysis, agent assist, post-call wrap-up, outbound communication, and full transcription all came along. The shift from the original Connect to Connect Customer is a shift from AI as a feature to AI as the operating model.

    The three new products start from that same premise, except they aren’t retrofits. They were built from scratch for agentic execution.

    Three Reasons the Benefits Case Is Credible

    Vendor AI announcements are easy to be skeptical of. This one has a few things working in its favor.

    Scale. Amazon Connect Customer handled 20 million interactions per day and processed 12 billion AI-powered minutes of conversation last year. That’s not a pilot. The new products are built on the same infrastructure. For enterprise buyers who have watched AI proofs of concept collapse under production load, operational scale at this level is a legitimate differentiator.

    Domain expertise embedded in the product. Amazon didn’t hire supply chain consultants to build Connect Decisions. It extracted the models and decision frameworks from its own retail and logistics operations — systems managing demand planning across more than 400 million SKUs. Connect Talent draws from Amazon’s process for hiring 250,000 seasonal workers in a single season. Connect Health is built on the clinical AI running at One Medical, which has now processed more than one million ambient documentation visits. This is proprietary operational knowledge baked into the product, not a general-purpose LLM applied to a new domain. That distinction matters for buyers evaluating whether a product will actually understand their problem.

    Integration with existing AWS infrastructure. For organizations already running on AWS, these products inherit the identity management, access controls, audit logging, and compliance certifications already in place. Buyers don’t start from zero on security posture or governance. That’s a real reduction in implementation risk, particularly in regulated industries like healthcare and financial services.

    On the Branding: Confusing Short-Term, Coherent Long-Term

    The name “Amazon Connect” has strong recognition in the enterprise market specifically as a contact center product. Adding supply chain, hiring, and healthcare products under the same name will require education.

    That said, the decision is defensible. The Connect products share a common architecture and a common design philosophy. AWS is calling that philosophy “Humorphism” — building products designed around how humans and AI agents collaborate, rather than how humans use static tools. Agents ask clarifying questions. They capture the reasoning behind manual edits. They improve over time as they learn from user decisions. Every Connect product is designed to work this way.

    The naming creates a coherent category: all Connect products are agentic, all are built on Amazon’s internal operational experience, and all are designed for line-of-business adoption rather than IT-led implementation. That’s a real product strategy, not just a logo change.

    Buyers evaluating these products should simply be explicit in conversations with AWS about which Connect product they mean. In the short term, that’s a small friction. In the long term, a unified family brand is cleaner than four separate product names with no connective tissue.

    The Open Questions That Need Answers

    Pricing is TBD. AWS did not address how these products will be priced or licensed. For supply chain and hiring products competing with established enterprise software, pricing model matters significantly. Per-transaction, per-user, and consumption-based models all create different budget implications. Enterprise buyers should not evaluate these products without getting pricing clarity first.

    The ERP and HCM question is unresolved. Connect Decisions targets supply chain planning. Connect Talent targets high-volume hiring. Both markets have entrenched incumbents — SAP and Oracle on the ERP side, Workday and Oracle HCM on the talent side — that already hold enterprise data and run existing workflows.

    The question isn’t whether Amazon can build better AI. The question is how Connect Decisions and Connect Talent interact with the systems enterprises already have. A few scenarios are possible, and AWS hasn’t clarified which one applies. The existing ERP or HCM system could become a data source that feeds the Connect agents. The incumbent vendor could build its own agents that call Connect products as tools. Or both systems end up running parallel agent workflows that need to be orchestrated together. Each of these plays out differently for buyers in terms of integration complexity, data governance, and total cost of ownership.

    The demos shown at the event depict Connect Decisions and Connect Talent operating as primary systems of action — generating demand plans, running interviews, surfacing candidate assessments. That implies some displacement of existing workflow software, at minimum for the activities these agents handle. Whether that displacement requires wholesale replacement of incumbent systems, or whether it can coexist alongside them, is not clear from what was announced. Buyers who already run SAP or Workday should press AWS specifically on this before evaluating further.

    What to Do With This Information

    If you’re an existing Amazon Connect customer, evaluate what the next-generation Connect Customer capabilities mean for your current deployment before looking at the new products. The AI-across-the-journey architecture is a meaningful shift from the original product, and understanding it fully is the right starting point.

    If you’re in supply chain, high-volume hiring, or healthcare and are currently underserved by your existing software, these products are worth a serious look. The domain expertise and scale credentials are real. Get pricing clarity and understand the integration model before committing.

    If you’re running SAP, Workday, or another incumbent system in these domains, don’t assume this announcement is irrelevant to you. The better question to ask your existing vendor is: what is your agent strategy, and how does it interact with what AWS just announced?

    The question isn’t whether Amazon Connect should be a family of products. The question is whether or how to make your current stack work alongside it.

    Subscribe to my AI with Maribel Lopez podcast on your channel of choice at https://www.buzzsprout.com/194744.