Step 1 of 3
The screen.
One product line, one application class. The screen reads every candidate product we can find in the class and sorts it against the criteria your FAE defined.
It is the step the other two build on, and the one with the most evidence behind it: it is the system described on the FPGA screening page, tested on public products against a stand-in profile.
A product line, an application class, and an engineer's time.
The product line's datasheet and the parts it can realistically displace come from you; nobody knows them better. The application class is the market you want to win in: industrial machine vision cameras, servo drives, on-board chargers.
- The product line's datasheet and the part families it can replace
- The application class, and any products you already know carry a replaceable part
- An FAE to sign off the criteria and review the flagged cases
Criteria, retrieval, extraction, fixed questions, routing.
The criteria become a fixed set of questions. For each product, documentation is collected and kept, values are extracted into a fixed table with the source text, the questions are answered against the table, and the product is routed.
- Supported match: the stated requirements support the part
- Supported exclusion: a stated requirement rules the part out, with the quote
- Flagged for review: a key value is missing or the checks disagree
The flagged cases go to your FAE with the checks, the quotes and the open questions. Not every record is checked by an engineer; the ones the evidence cannot settle are.
Three lists, built from product records.
Each entry is a product record: what the product is, the checks against your criteria, the source for each value, what is still unknown, and any supported evidence on timing.
- A shortlist for qualification
- An exclusion list with the reason per product
- A review queue of flagged products
What is inside, and when.
Datasheets state what a product needs and almost never name the device inside. Where no filing, teardown or posting fills that field, the record says unknown. Technical fit says nothing about when a socket might change; timing is assessed separately and only from evidence.
- Missing evidence is not evidence of incompatibility
- A fit is not a purchasing window
- The flagging is still being tested; no accuracy figure is published until an expert-labelled benchmark has run
Next steps.
- The regional map aggregates these records by region
- The subscription keeps them current in your CRM
- The FPGA screening page shows the system as built
The service · Step 2: the regional map · Step 3: the subscription · FPGA product-fit screening · How the system works
Start a screen