Intelli Catalogue Ver 10 0 0 May 2026

They trained a small language model on 14 million internal part descriptions, plus public standards (ETIM, UNSPSC, eCl@ss). The model could suggest missing attributes with 94% accuracy. This became the IntelliClassify module.

It was, as Elena Voss wrote in the release notes’ final line: “A catalogue should not be a museum of parts. It should be a living, thinking partner in how you build things.” intelli catalogue ver 10 0 0

Priya gets an alert: “Your preferred supplier for capacitor C112 has a 12‑week lead time. Here are three alternates from existing catalogue items with stock at Warehouse B.” She approves a swap in two clicks. They trained a small language model on 14

Prologue: The Breaking Point For nearly a decade, Intelli Catalogue had been the quiet backbone of mid‑tier manufacturing and distribution. Version 9.x was reliable—a workhorse that digitized parts lists, routed approvals, and kept BOMs (bills of materials) from turning into chaos. But by late 2025, the cracks were showing. It was, as Elena Voss wrote in the

Carlos builds a custom pump assembly for a client. The portal shows only compatible parts, live pricing, and regulatory flags (e.g., “This motor is not RoHS compliant for EU delivery”). The quote is 100% accurate and generated instantly. Under the Hood: Key Technical Stats | Feature | v9.x | v10.0.0 | |---------|------|---------| | Max catalogue size | 500k SKUs | 20M SKUs | | Search latency (p95) | 2.3 sec | 0.18 sec | | Integration types | 6 (file‑based) | 34 (live APIs) | | AI attribute fill rate | none | 91% | | Concurrent users | 50 | 2,000 | | Downtime for upgrades | 4 hours/month | < 2 seconds (live migration) | The “Oh No” Moment Two weeks after GA, a major aerospace customer reported that their BOM revision history had vanished after upgrade. The root cause: a migration script assumed all BOMs used “engineering revision” as the primary key, but the customer had used “date+approver” as the composite key.

Live connectors were written for SAP, Oracle, Salesforce, and 12 common ERPs. A key innovation was the change propagation protocol : when procurement updated a supplier lead time, the change rippled to all BOMs and quotes within seconds.