BPM Microsystems · Automation / AI intern · 2026
PDR Builder
A pipeline that turns semiconductor datasheets into pin-driver requirement files, with deterministic checks and human review.
- Python
- LLM extraction
- Deterministic rules
- Human review
- Salesforce
System
- Datasheet
- Pin and protocol extraction
- Deterministic checks
- Human review
- .pdr + Excel
Problem
A pin-driver requirements file (PDR) tells BPM’s programmer hardware how to connect to a chip: which pins are power, which carry signals, and which protocol to use. Writing one by hand is slow, and mistakes are easy to miss. The pipeline needed to send uncertain pins to a person for review instead of guessing.
What I built
- A two-pass pin extractor that reads both the PDF text layer and page images, then reconciles the two with deterministic rules and lint checks.
- Protocol selection that checks the chosen pins against the chip package and sends incomplete results to review.
- A local review app where engineers approve the extracted data, plus generators for production .pdr files and Excel workbooks.
- Scoring against hand-made answer keys that counts abstentions, gaps, and silent errors separately, and a backtest on 64 historical designs.
Results
- historical design validations passed
- 27/27
- noise errors per design
- 0.09
- silent errors on scored pin cases
- 0
Limits
The model-based extraction always goes through human review. Recall can only be measured on devices that have a complete answer key.