INDUSTRY FIELD GUIDE
Relay and industrial control data for AI rating-field scope
Relay and industrial control manufacturing has a defined Census scope.
NAICS 335314 · Relay and Industrial Control Manufacturing
Relay and industrial control manufacturing has a defined Census scope. An original control-component exercise can test whether an assistant preserves the exact field and variant named by a source. Census relay and control scope
Create fictional relay cards, variant codes and a customer request. Put separately defined coil and contact fields beside each other. Ask which entry answers each requested property. Include a similar variant with a different suffix and a report missing that suffix. The key should retain the ambiguous association instead of selecting a favorable nearby value.
Annotate component, variant, property, unit, source scope and document version. Evaluate with a new card layout and an explicit glossary. Score one rating field substituted for another, a family name used as exact variant identity and a missing suffix guessed independently. A complete case should support the requested comparison with every relevant field cited.
Use original tables and invented values without energizing a component. Customer circuits, licensed specifications, proprietary firmware and supplier reports need appropriate authority and qualified review. Describe the field-selection task and checked key in the contributor proposal. Establish buyer requirements before preparing a larger archive or additional capture.
Discuss this original manufacturing sample with Fiund
Original Fiund exercise
The control-side field is not a contact rating
Original mock relay cards use neutral class codes only. No real electrical values appear.
| Record | Source | What it records |
|---|---|---|
| 1 | Request | Relay R4 with control class C2 and contact class K3. |
| 2 | Variant A | R4, control C2, contacts K1. |
| 3 | Variant B | R4, control C4, contacts K3. |
Question for the model
Which variant satisfies both roles?
Show the reference answer and checks
Neither. A satisfies the control requirement but has K1 contacts. B satisfies the contact requirement but has C4 control. Records 1–3 call for the two role-specific fields on the same variant; combining one from each would invent a configuration.
- Treating a class token as independent of role
- Mixing the control field and contact field from different items
Fields to preserve
- control_class
- Records the input-side requirement
- contact_class
- Records the switched-side field
- variant_key
- Keeps both fields tied to one product
Test another case
Give a variant with two independent contact groups; require the requested group label before matching its class.
No actual ratings, wiring, relay selection or operation advice.
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.