Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Dell edition of November 5, 2026

Independent reportingEmergingNew this fortnight

SiliconANGLE summit interview: Texas A&M System and TEES describe Dell-built, state-funded IGNITE AI/HPC platform with AMD GPUs in Equinix Dallas, citing ~5–10x neocloud cost and security-first implementation

Texas A&M University System and Texas A&M Engineering Experiment Station (TEES), with Dell Technologies and AMD; hosted at Equinix Dallas · Higher education / state research agency (AI and HPC) · Texas, United States (Equinix Dallas facility)

Publisher
SiliconANGLE / theCUBE (Ryan Stevens)
Original publication
2026-11-04
Source retrieved
2026-11-06
Event date
2026-11-04
Read original source

What happened

In a Nov. 4, 2026 SiliconANGLE/theCUBE interview from the AI Cybersecurity & Resilience Summit, Texas A&M System CIO Vince Kellen and TEES CIO Casey Bryan described IGNITE (Innovative Growth in Next Generation AI Technology Ecosystem), a state-funded AI and HPC platform TEES is building with Dell Technologies and AMD GPUs inside an Equinix data center in Dallas. Bryan said existing resources are severely underpowered. Kellen said retail neocloud AI compute can be 5 to 10x the cost of conducting the same science on controlled infrastructure. TEES, as a state agency, follows NIST 800-53 and 800-171 and Texas Administrative Code 202 and wants IGNITE ready for CMMC Level 2. Bryan said security workshops with Dell’s implementation team came first and were affirmed by the architecture review board. No performance results, contract value or server SKUs are reported. Disclosure: theCUBE was a paid media partner; Dell sponsored coverage but is stated to lack editorial control.

Why it matters

Direct higher-education and state-agency signal: a Texas state-funded research AI platform on Dell infrastructure with explicit cost, control-framework and security-sequencing lessons for other public research institutions. Not a measured deployment outcome.

Evidence and measured results

On-the-record CIOs in an independent trade interview; economic comparison is a leadership estimate without published methodology; hardware details limited; paid-media disclosure applies.

Limitations and uncertainty

No results yet; 5–10x cost claim is not a TCO study; SKUs undisclosed here; theCUBE coverage Dell-sponsored with disclosure; earlier July vendor PR exists but this interview is the new independent why-now.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Public research universities need more AI/HPC capacity for federal and state work without paying retail neocloud prices or losing control of sensitive data.
Stakeholders
  • System CIO
  • Experiment-station CIO
  • Vice president for research
  • Campus research computing
  • State agency security/compliance
  • Procurement
Discovery questions
  • Which research workloads cannot go to a commercial neocloud today and why?
  • What NIST, CMMC or state controls must a shared research platform inherit?
  • Where will the system be hosted and who operates the facility?
  • How will security be sequenced into Dell implementation workshops?
Value hypothesis
A state-funded, Dell-built on-premises platform may cut AI compute cost versus retail neoclouds and embed compliance earlier; the 5–10x figure is a CIO estimate, not a measured TCO study.
Potential engagement
A bounded sovereign-AI readiness assessment for one research computing program covering control frameworks, hosting model and security-first implementation sequencing with Dell.
Unsupported claims
  • Guaranteed 5–10x savings versus any cloud
  • That IGNITE is already CMMC Level 2 certified
  • Measured research throughput gains
  • That Equinix hosting equals full data sovereignty

Pre-sales engineering

Role takeaway
Fit
Fits R1/public research agencies that must support mixed-sensitivity federal and state AI/HPC workloads under NIST and state security baselines.
Architecture and integration
Dell-built AI/HPC stack with AMD GPUs in an Equinix Dallas facility, operated as shared infrastructure with policy-based access; detailed PowerEdge SKUs are not specified in this report.
Prerequisites
  • State or institutional funding for capacity
  • Mapped control set (NIST 800-53/800-171, TAC 202, CMMC target)
  • Architecture review board
  • Facility and network path to the colocation site
Constraints
  • Colocation is not fully on-campus sovereignty
  • Hardware bill of materials not disclosed here
  • No published performance or cost baselines yet
  • Federal program requirements vary by sponsor
Security
TEES wants seamless researcher access while inheriting agency controls and targeting CMMC Level 2; security workshops with Dell were scheduled before other operational design.
Proof of value
  • Compare unit cost of representative jobs on current clusters vs quoted neocloud rates
  • Verify control inheritance in architecture review artifacts
  • Pilot one regulated workload before broad enrollment

Delivery

Role takeaway
Work
Stand up a security-first shared AI/HPC platform with Dell implementation, define researcher onboarding that hides inherited controls, and operate the Equinix-hosted environment under TEES governance.
Dependencies
  • Dell implementation workshops and delivery
  • AMD GPU supply
  • Equinix facility readiness
  • Architecture review board approvals
Ownership
TEES CIO organization as state-agency operator, with Texas A&M System CIO alignment.
Skills and adoption
Researchers should consume the platform without learning every inherited control; operators need zero-trust and CMMC-oriented skills.
Governance checkpoints
  • Security foundation approved before operational components
  • Architecture review board sign-off
  • Control inheritance mapped to NIST/TAC/CMMC targets
  • Data classification before project onboarding
Acceptance criteria
  • Proposed: security workshops complete before production workloads
  • Proposed: documented control inheritance for enrolled projects
  • Proposed: researcher access path that does not require per-user control navigation
  • Proposed: cost tracking vs prior underpowered systems
Risks
  • Security bolted on late if sequencing slips
  • Colocation or supply delays
  • Cost claims overstated without TCO methodology
  • Researchers blocked by opaque access policy

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Shared Dell-built AI/HPC capacity with AMD GPUs in colocation, intended for mixed-sensitivity research under policy-based access rather than per-project silos.

Governance

Who approves, reviews and stays accountable for outcomes?

Control inheritance (NIST, TAC 202, CMMC L2 target) should be designed so researchers do not navigate every control; architecture review board affirmed security-first sequencing.

Security and privacy

What data, permissions and controls need testing?

Physical protection via Equinix plus agency control baselines; colocation and shared tenancy still require careful data classification and access policy.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Aims to expand research capacity for faculty and students without forcing them to administer inherited security controls.

Procurement

What should contracts, pricing and exit terms secure?

State-funded build with a named OEM integrator; peer institutions should separate facility, GPU supply and services line items and require security milestones in statements of work.

Operating model

Which teams own the service once it runs?

Positions TEES as operator of a shared sovereign research platform; security foundation before operational components is the stated delivery pattern.

Publication history

  1. 2026-11-05Dell · Issue 082 resources
Read preserved resource versions (JSON)

Stable resource ID: texas-am-tees-ignite-sovereign-ai-dell-amd-equinix-siliconangle-20261104