Solution

Failure Prediction & Diagnostics

When a card fails today, nobody can say which logic caused it. Fluid Silicon measures every element, so a fault has an address, a history and a forecast.

An FPGA accelerator card, drawn in isometric view

Measured impact

On production shells, at realistic utilization.

< 20 ps
per-link measurement precision
> 20%
random variation at 16, 14 and 7 nm: why identical cards fail differently
6+ years
cards now stay in service, beyond what their timing models assumed

*Fluid Silicon measurements. Varies with variation pattern, workload, vendor and device age.

Degradation Prediction

Which card fails next, and when.

  • Every element measured about once a second for the life of the card.
  • A per-card aging curve fitted to its temperature history.
  • A time-to-threshold that feeds replacement and capacity planning.
  • Cards aging faster than their neighbours flagged early.

Prediction, not a schedule

Replacing boards on a fixed schedule retires healthy cards and misses failing ones. A forecast per card replaces the schedule.

Illustrative aging model for one card at three temperaturesPath delay increase over years in service. Measured points for the first three years lie on a fitted aging curve, projected forward. At 70 degrees Celsius the projection crosses the 6 percent alert threshold at about 3.8 years, at 55 degrees at about 7.6 years, and at 45 degrees beyond 10 years.0%2%4%6%8%0246810Years in servicePath delay increaseAlert thresholdToday45 °C: > 10 yrs55 °C: 7.6 yrs70 °C: 3.8 yrs
45 °C55 °C70 °C
Illustrative model for one card.

Error Attribution

A fault with an address.

  • Per-element slack history around the time of an error.
  • The weakest element on the card, and how long it has been weakening.
  • Evidence that separates a timing fault from a software or thermal event.
  • Reports your reliability team can attach to a ticket.

Before the error travels

An error in one card can take capacity offline or propagate downstream. Attribution shortens the path from symptom to cause.

One card's health with its weakest element and history. Illustrative screen.

Outlier Detection

The tails of the fleet.

  • Each card's weakest element compared across the fleet.
  • Systematic and random variation separated from aging.
  • Cards far below the family median surfaced first.
  • The same comparison on AMD and Altera parts.

Variation at scale

At 16, 14 and 7 nm, random variation alone exceeds 20%, on top of systematic variation across the die. Measuring more chips finds more tails.

A margin per chip instead of one for the fleetThree chips measured separately, each with narrow distributions of LUT and carry link delays, and each signed off at its own measured delay plus under 20 picoseconds of error and drift. The fleet-wide worst-case corner is shown faintly on the right, no longer needed.Measured: a margin per chipFleet corner, no longer neededChip AChip BChip CPer-chip margin: error + drift, under 20 psPath delay →
LUT linksCarry linksPer-chip sign-off
Illustrative, not to scale.

Evidence for Root Cause

Data your vendors can act on.

  • Per-element measurements from the day a card entered service.
  • Temperature and operating-point history alongside timing.
  • Exit characterization when a card leaves service.
  • One vendor-neutral format for your team and your suppliers.

Feedback to the silicon vendor

A card returned with a measured history is a different conversation from a card returned with a symptom.

An FPGA accelerator card, drawn in isometric view

FAQ

Common questions.

Sensor architecture, deployment mechanics and calibration methods are shared with evaluation partners under NDA.

What kinds of failure does this predict?

Timing failures from variation and wear-out: logic that has slowed past its margin. It does not predict mechanical, power-supply or radiation events; it complements the measures you have for those.

How is an error attributed?

Every logic element has a measured slack history, so an error is checked against the elements that were weakest at the time. The result is evidence, not inference.

Can it tell aging from a bad batch?

Yes. Aging shows as a trend in a card's own history; a bad batch shows as an outlier at incoming characterization, before the card ages at all.

Does monitoring affect our design's timing?

The health layer adds under 2% delay and occupies under 1% of LUTs on a production shell. It does not interfere with the design's computation.

How often is each card measured?

A full sweep of every logic element takes about a second and runs while the design computes. The interval between sweeps is yours to set.

Which devices are supported?

AMD 7-series, UltraScale and UltraScale+ today, with select Altera Agilex 7 devices; more families in development. See device support.

Measure a device at speed, live.

A 30-minute session: in-system slack measurements on a supported AMD or Altera device, and what an evaluation on your boards involves.