UCP Engineer Guide
Use this section when reading UCP pillow block bearing unit results. Use this section with result interpretation, technical snapshot, and the product field guides.
How To Read A UCP Result
Section titled “How To Read A UCP Result”- Confirm the request is for a supported UCP pillow block unit, not UKP or another mounted bearing family.
- Confirm whether the reference was resolved by part number or dimensions.
- Check
drop_inand the score band:GREEN,YELLOW, orRED. - Read
gate_reportfor hard gate failures. - Read
highlights,missing_info, anddifferences.rowsfor risk flags. - Compare the technical snapshot fields for
d,H,J,N, bolt size, locking style, housing construction, ratings, and mass. - Decide whether the candidate can be used, needs review, or must be rejected.
- Do treat
GREENas the strongest UCP candidate class, but still check evidence and differences. - Do review every
YELLOWrow before suggesting it as a replacement. - Do use
REDrows as diagnostics unless a non-drop-in review workflow explicitly asks for them. - Do confirm mounting dimensions
d,H,J, andNbefore relying on a candidate. - Do check load ratings when the application load is known.
- Do explain locking style or housing differences in plain language.
- Do not document UKP as supported by the UCP matcher.
- Do not call a
YELLOWrow a clean drop-in without naming the risk flags. - Do not recommend a
REDrow as a replacement. - Do not ignore mounting hole
Nsafety. - Do not use score alone to override hard gates.
- Do not hide missing bolt, housing, locking, or load evidence.
Status Next Actions
Section titled “Status Next Actions”| Status | Engineer action |
|---|---|
OK | Read band, gates, risk flags, and differences before recommending. |
AMBIGUOUS_MATCHES | Ask for exact part number, bore, housing size, or key mounting dimensions. |
INPUT_RECHECK_REQUIRED | Resolve conflicting bore, dimensions, or family clues before matching. |
NO_REFERENCE | Request part number, datasheet, nameplate, or measured d/H/J/N. |
ERROR | Do not interpret candidates; retry or escalate with payload. |
Tag Next Actions
Section titled “Tag Next Actions”| Tag | What to do next |
|---|---|
RISK_L_FOOTPRINT | Confirm base length and available mounting footprint. |
RISK_LOCKING_STYLE_MISMATCH | Confirm shaft locking requirements and maintenance preference. |
RISK_HOUSING_CONSTRUCTION_MISMATCH | Check housing material/construction against application conditions. |
RISK_DYNAMIC_LOWER | Verify dynamic load requirement before use. |
RISK_STATIC_LOWER | Verify static load requirement before use. |
RISK_WEIGHT_DIFFERENT | Confirm weight difference is acceptable for mounting/support. |
RISK_VARIANT_TOKENS_DIFFER | Compare suffixes and variant features against the original. |
Example Workflow
Section titled “Example Workflow”When a result is YELLOW because RISK_LOCKING_STYLE_MISMATCH and RISK_DYNAMIC_LOWER appear:
- Tell the engineer the candidate passed core geometry but is not a clean replacement.
- Compare locking method with the installed unit.
- Compare dynamic load rating against the application.
- Recommend only after the differences are accepted.
Never Claim
Section titled “Never Claim”- Never claim “same bearing unit” from bore alone.
- Never claim “drop-in” when
N,H, orJis missing or failed. - Never claim lower load rating is acceptable without application review.