CASE 01Equipment re-qualification
After a firmware or parameter change.
Explore caseNovigens develops Brain, software that gives equipment the ability to explain its own alarms, deviations and process/test results from the observables and design artifacts that already exist, even when your FMEA has missed it.
Unplanned downtime
An unplanned stop is explained by an engineer who knows the machine, and those engineers are scarce and burning out. The usual fix, agentic AI and observability tools, requires the same engineers to author the machine's ontology and procedures first, and when the next design iteration ships, everything they wrote goes down the drain.
That calls for machines that can explain themselves when the input tray jams or the bond head drifts.
That engineer works days, has retired, or is the OEM's field engineer in another time zone.
The ontology and procedures the tools run on have to be authored by hand, and the knowledge keeps changing.
The ontology is derived real-time from the design artifacts and observables instead of being authored by hand. And now, the previously burnt-out engineers are being supported.
Use cases
Software on an edge computer next to the machine. In production on semiconductor backend equipment (test handlers, probers, die attach, wire bonders); applies to SMT lines. Explore Brain.
CASE 01After a firmware or parameter change.
Explore case
CASE 02When an alarm stops the line.
Explore case
CASE 03When the test data sits in files.
Explore caseThe program starts with one machine class and a representative sample of its design artifacts under NDA. Brain then derives the full model on the floor.