Turn the device spec into requirements a machine can read. Upload the datasheet or the requirements spreadsheet, or sync a Jama Connect project, and each requirement becomes a typed row holding the limits, forced condition and test number the source states; anything the source leaves out you fill in once, in review. The generated program, the limit checks and the production data then all join on those rows.
A requirement in ATE·IQ™ is not a paragraph of prose. It is a row with a lower and an upper limit, a unit, the stimulus to apply and a test number, and every surface downstream reads those fields directly: generation keys every test to its requirement's test number, traceability compares the spec's limits with the program's and with what production recorded, and the IG-XL agent answers whether a spec change reached the program and the lots from the same rows.
| Source | How it is read |
|---|---|
| Spreadsheet (.csv, .xlsx) | Column by column, so each number comes straight from the cell that holds it. |
| Document (.pdf, .docx) | The model reads the whole text under one instruction (leave a value empty rather than guess) and reports how much of the document it covered. Pin names and supply rails are captured when stated. |
| Plain text (.txt, .md) | Each requirement, its title and its category are captured; the numbers are left for you to fill in during review. |
| Jama Connect | Synced over its REST API with credentials stored encrypted. |
| Hand entry | Recorded as a person's decision. |
Every row lands in review tagged with where its numbers came from, so you know which to audit first: limits the model read are flagged, and a limit you change in review is recorded as yours. A document that yields no requirements raises a warning instead of showing a silent empty table.