Diagnose an asset and source the right replacement part
A 5-step recipe with Aquant. We can help you get access.
Recipe · 5 steps
Diagnose an asset and source the right replacement part
with Aquant
Guard on observation_existence, rank likely next symptoms, then walk the parts chain from catalog lookup through detail to sourcing.
- Guard — verify Aquant knows this symptom before acting on it.
- Rank the most likely next symptoms for this asset, with how to check each.
- Find candidate parts from the tenant catalog.
- Pull detail for the selected catalog entry — pass the catalog data through, do not re-derive it.
- Find where the part can be sourced.
What you'll need to have ready
- tenant_id: [TEMPORARY] Aquant tenant identifier.
- asset_id
- observation_name: The reported symptom.
- triage_product_id
- question: The technician's natural-language ask.
- model: Equipment model
- top_n: How many symptom predictions to return.
For your developer
Arazzo workflow aquant:diagnose-and-source-part, 5 operations: observation_existence → next_symptom → part_catalog_lookup → part_info → part_sources. Specs on APIs.io.