Why is a single vector database mathematically incapable of answering all enterprise retrieval needs across systems like FieldDesk and PolicyDesk?
Day 25: Route Across Multiple Knowledge Sources
Route Across Multiple Knowledge Sources
Loading lesson content...
In FieldDesk, an unstructured manual specifies ISO VG 46 oil, while a structured asset maintenance record specifies that pump P-401 was upgraded to ISO VG 68. How does the multi-source router resolve this contradiction during context assembly?
A technician asks FieldDesk: 'Pump P-401 is vibrating at 9.2 mm/s. What is the allowable limit, root cause, and replacement bearing part number in warehouse stock?' Answering requires SQL CMMS, SCADA telemetry, vector manuals, and ERP inventory. What execution topology must the orchestrator implement?