Electronic Components · 18 attributes

Semiconductor product attributes

Semiconductor attribute template: device type, package, voltage and current ratings, Rds(on) with test conditions, lifecycle status and moisture sensitivity.

Download CSV template JSON Editorial reference

Semiconductor records carry more conditional data than almost any other category. A MOSFET's on-resistance, a diode's forward voltage and a transistor's current rating all depend on the test conditions printed next to them. Supplier summaries often keep the number and drop the gate voltage, drain current or case temperature, which makes two devices look equivalent when they are not.

Packages are named inconsistently across the industry. The same physical outline can appear as a JEDEC name, a JEITA name and several manufacturer-specific case codes, while the pin count and tab arrangement vary within one family. Keeping a normalized package value and the manufacturer's own package name side by side lets a buyer search by either without losing precision.

Supply and handling data are as important as electrical data. Lifecycle status, last-time-buy dates, moisture sensitivity level, packaging form, automotive qualification and export classification decide whether a part can be designed in, stored, assembled and shipped. Country of origin can mean the wafer fab or the assembly site, and customs and customer questions do not always refer to the same one.

The semiconductors attribute template

18 candidate fields in 4 groups, ordered the way a record gets built: identify the item, capture its specifications, then record fit and the evidence behind any claim. 7 are marked Core: without them the item cannot be identified or filtered. Example values show the expected format only; they do not describe a real SKU.

Identity

Which exact item, variant and pack this record describes.

Check before use: Preserve leading zeros and punctuation, validate against the manufacturer record, and check the GTIN check digit and packaging level before linking.

Attribute Type Priority Example format
Manufacturer Part Number (MPN) manufacturer_part_number_mpn Identifier Core NFX5522-DPK
GTIN-14 / UPC gtin_14_upc Identifier Core 10614141600042

Technical specifications

Measured or rated values that must travel with their unit and test conditions.

Check before use: Store the number and unit separately. Convert only when the source unit and test conditions are known.

Attribute Type Priority Example format
Operating Junction Temperature (Tj) operating_junction_temperature_tj Text · °C Core -55 °C to +175 °C
Drain-Source Breakdown Voltage (Vdss) drain_source_breakdown_voltage_vdss Number · V Buyer decision 55
Continuous Drain Current (Id) @ Tc = 25°C continuous_drain_current_id_tc_25_c Number · A Buyer decision 42
Rds(on) Max @ Id, Vgs rds_on_max_id_vgs Number · mΩ Buyer decision 22 mΩ @ Id 25 A, Vgs 5 V
Total Gate Charge (Qg) Max @ Vgs total_gate_charge_qg_max_vgs Number · nC Buyer decision 48 nC @ Vgs 5 V
Moisture Sensitivity Level (MSL) moisture_sensitivity_level_msl Controlled list Channel / evidence 1 (Unlimited)

Selection attributes

The type, material and option choices buyers filter and compare on.

Check before use: Map supplier wording to a governed vocabulary only after checking the source text and which variant it applies to.

Attribute Type Priority Example format
Device Type device_type Controlled list Core MOSFET, N-Channel
Package / Case package_case Controlled list Core TO-252-3, DPAK (2 Leads + Tab)
Supplier Device Package supplier_device_package Text Core DPAK
Packaging (Shipping Form) packaging_shipping_form Controlled list Core Tape & Reel (TR)
Die Technology die_technology Controlled list Buyer decision Silicon
Product Lifecycle Status product_lifecycle_status Controlled list Channel / evidence Active

Evidence & compliance

Listings, standards, classifications and origin claims that need a document behind them.

Check before use: Link the manufacturer document or label with its edition or date. Never copy a certification from a neighboring SKU.

Attribute Type Priority Example format
Automotive Qualification automotive_qualification Controlled list Channel / evidence AEC-Q101 Qualified
RoHS / REACH SVHC Status rohs_reach_svhc_status Controlled list Channel / evidence RoHS compliant; no SVHC above 0.1 % w/w
ECCN eccn Identifier Channel / evidence EAR99
Country of Origin (Assembly / Test) country_of_origin_assembly_test Controlled list Channel / evidence Philippines

Normalize supplier values

The same value arrives in many spellings. Map each raw string to one governed value, and keep the raw text beside it so a reviewer can see what the supplier actually wrote.

Package / Case

TO-252DPAKSC-63SOT-428TO-252AAD-PAK

Normalized to TO-252-3, DPAK (2 Leads + Tab)

Rds(on)

0.022 Ω22 mΩ22mOhm0.022 ohm max22 milliohm

Normalized to 22 mΩ (max) @ Vgs = 5 V, Id = 25 A

Product Lifecycle Status

NRNDNot For New DesignNFNDNot RecommendedNot Rec. for New Designs

Normalized to Not Recommended for New Designs (NRND)

Often missing from supplier files

These fields are commonly absent from price lists and basic feeds, even though the information usually exists in a datasheet, label or installation manual. Treat an empty value as a request for evidence, not as permission to fill it from a similar model.

  • Country of Diffusion (Wafer Fab)
  • Rds(on) Test Conditions (Vgs, Id)
  • Moisture Sensitivity Level and Floor Life
  • Last-Time-Buy Date / Discontinuance Notice
  • Automotive Qualification (AEC-Q100 / AEC-Q101)

Questions the record must answer

Buyers and counter-sales reps choosing semiconductors ask questions like these. Each one needs a specific field, sourced for the exact variant.

  • Will this MOSFET be fully on with a 5 V gate drive from my microcontroller?
  • Does this DPAK part fit the footprint of the one we are replacing?
  • Is this device still active, or is a last-time-buy date announced?
  • How long can the reel sit out after opening before it needs baking?

From supplier file to record

  1. Resolve identity first. Link the supplier SKU, manufacturer part number and packaging identifiers without merging distinct variants or pack sizes.
  2. Extract with the source attached. Pull values from rows, tables and datasheets, keeping the raw text, unit and page or row reference.
  3. Map to your classification. Assign the ETIM, ECLASS, UNSPSC or internal class your company licenses, and keep the supplier's original terms.
  4. Review, sync and watch. Hold conflicts and safety-related values for a category expert, write approved values to ERP or PIM, and recheck when the supplier sends a new file.

For the full method, see how to build a category attribute template and the category catalog gap audit.

FAQ

Why store both a normalized package and the supplier device package?

The normalized package lets buyers filter across manufacturers, for example every TO-252 device regardless of who makes it. The supplier device package preserves the manufacturer's own name, which may encode pin count, tab or thermal pad details that the normalized value hides. Keep the normalized value as a controlled field with synonyms such as DPAK and SC-63, and store the manufacturer's name as text. Use the manufacturer's package drawing to confirm footprint compatibility rather than the name alone.

Should Rds(on) be stored as a number or as a number with conditions?

Store the number and its conditions together. Rds(on) varies with gate-source voltage, drain current and junction temperature, and manufacturers quote it at different points. A value of 22 mΩ at 10 V gate drive is not comparable to one quoted at 4.5 V. Keep the maximum value as a number with a unit, and hold gate voltage, drain current and temperature as linked condition fields. The same pattern applies to gate charge, forward voltage and similar parameters.

What values should a product lifecycle status field allow?

Use a short controlled list that maps cleanly to manufacturer notices, for example active, not recommended for new designs, last time buy, obsolete and preview or pre-release. Map supplier phrases such as NRND and NFND to the governed value and keep the original text. Store the last-time-buy date and the product change or discontinuance notice reference as separate fields, and record when the status was last checked, since it changes over time.

Should country of origin be one field or two for semiconductors?

Two fields are usually safer. A device may be diffused, meaning the wafer is fabricated, in one country and assembled and tested in another. Customs rules and customer questionnaires can refer to either location, and the answer depends on the applicable rules. Store diffusion country and assembly or test country separately, taken from the manufacturer's documentation, and leave the determination of origin for customs to the applicable regulations and the manufacturer's declarations.

Claro

See where your catalog breaks — free

Claro runs this automatically: resolve identity, fill missing attributes, validate updates, and write clean records back into your PIM/ERP. Upload a sample supplier file for a free catalog audit.

Get a free catalog audit

Related resources

More Electronic Components templates