UCP Examples

Input Type: Known Unit Part Number

User input:

Find replacements for Koyo UCP210FCD.

Captured fields:

Field	Value
identity.manufacturer	KOYO
query.selected_part_number	UCP210FCD

How to use it:

• This launches through the part-number path.
• Manufacturer improves confidence, but the selected part number is the main anchor.
• Engineer should still review suffix/variant meaning and result risk tags.

Input Type: Variant Part Number

User input:

I need a replacement for ASAHI UCPA209-26.

Captured fields:

Field	Value
identity.manufacturer	ASAHI
query.selected_part_number	UCPA209-26

How to use it:

• Treat the variant suffix as meaningful.
• Do not reduce this to only the base UCP/UCPA size.
• Review RISK_VARIANT_TOKENS_DIFFER if candidates differ by suffix or variant features.

Input Type: Dimension-Based Launch

User input:

No part number. Bore d is 50 mm, center height H is 57.2 mm, and mounting pitch J is 159 mm.

Captured fields:

Field	Value
core_dims_mm.d_mm	50
core_dims_mm.H_mm	57.2
core_dims_mm.J_mm	159

How to use it:

• This is the minimum dimension-based launch path.
• Ask for N hole diameter and L overall length next because they affect safety and footprint risk.
• If multiple references remain, handle as AMBIGUOUS_MATCHES.

Input Type: Requirements Added

User input:

Replacement must support 3000 RPM, be relubricatable, and have at least 35 kN dynamic rating.

Captured fields:

Field	Value
requirements.speed_rpm	3000
requirements.relubricatable_required	true
requirements.required_dynamic_C_N	35000

How to use it:

• These fields do not identify the UCP unit by themselves.
• They constrain candidate safety and can create warnings or blocks.
• Do not ignore load/speed requirements when interpreting a YELLOW result.