Skip to content

INDUSTRY FIELD GUIDE

Passive electronic component data for AI value and condition checks

NIST's SI guidance provides context for units and prefixes.

By Fiund · Updated 2026-11-05

NAICS 334416 · Capacitor, Resistor, Coil, Transformer, and Other Inductor Manufacturing

NIST's SI guidance provides context for units and prefixes. A component manufacturer can define an original task that retains the requested property, unit and test condition on a sample record. NIST SI-prefix context

Prepare fictional component cards, a sample report and a customer request. Use explicit exercise definitions for the units and conditions. Put a nominal value beside a measured sample observation. Ask which entry answers the request. Include a different property with a similar numeric value and a report lacking its specimen identifier.

Annotate component, nominal or observed status, property, unit, condition and sample. Evaluate with a new table layout and a supplied conversion rule. Score nominal values used as measurements, wrong-property substitution and unsupported sample association independently. A complete case should allow a reproducible comparison from the cited fields.

Use original tables and invented values without energizing components. Customer circuit designs, licensed specifications, proprietary test methods and outside reports need permission and qualified review. A licensing brief should identify the property-selection task and checked examples. Establish buyer requirements before preparing a commercial archive or commissioning additional capture.

Discuss this original manufacturing sample with Fiund

Original Fiund exercise

A nominal value and a condition-scoped result serve different purposes

Fictional component cards use abstract units and condition keys. No real circuit application appears.

Fictional records supplied to the evaluator
RecordSourceWhat it records
1RequestObserved value for specimen P2 under C1.
2Component cardP2 nominal 10 units.
3ReportP2 observed 9 units under C2; no C1 result.

Question for the model

Which value can fill the C1 observed field?

Show the reference answer and checks

Neither. Record 2 is nominal rather than measured, and record 3 observes a different condition. Keep 10 in the nominal field and 9 as C2 evidence. Record 1's requested C1 observation remains missing until a matching measurement is supplied.

  • Using nominal as a missing observed value
  • Dropping condition when reusing a result

Fields to preserve

value_type
Distinguishes nominal and observed data
condition_id
Scopes the measurement
specimen_key
Binds the record to the actual item

Test another case

Supply C1 for a sister specimen and require exact specimen scope rather than using the family value.

No actual component values, circuit design, testing instructions or electrical ratings.

Download this fictional example and answer key (JSON)

Discuss a contribution

Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.

Primary sources and further reading