A useful after-sales decision does not come from data volume alone. It comes from reliable acquisition, clear provenance and enough context for a technician to understand what the vehicle actually reported.
One architecture, two sources of context
XENTRON Ultra is the shared engineering core behind two purpose-built devices. XENCHECK Ultra supports the workshop by capturing diagnostic evidence from the vehicle. XENFLEET can add connected-vehicle context when it is installed, authorized and configured for that fleet. The two roles remain distinct even when their data is used in the same service process.
Workshop evidence from XENCHECK Ultra
The XENCHECK Ultra VCU communicates with supported vehicle networks through the DLC/OBD interface. Depending on the vehicle and enabled protocol coverage, it can capture the VIN, ECU inventory, DTCs, freeze-frame records and live values. Every item should retain its source, timestamp and acquisition context so later analysis can be traced back to the vehicle evidence.
Connected context from XENFLEET
Where XENFLEET is deployed and the customer has authorized the data flow, recent operating context can complement the workshop snapshot. This does not make telematics a substitute for a diagnostic test. It gives the technician another bounded source of evidence that may help explain when or under which conditions a symptom occurred.
Enrichment without losing traceability
Configured integrations may associate the technical record with available DMS, repair-order, campaign or parts information. Access depends on the customer's systems, APIs and permissions. Each added field must keep its source and freshness visible; missing context must remain missing rather than being inferred as fact.
AI assists; the technician decides
Rules and machine-learning models can group related signals, rank possible causes and highlight the next useful test. Their output is decision support, not an automatic diagnosis. A qualified technician validates the evidence, performs the required tests and approves the service action.
The right performance measures therefore cover the complete workflow: time to usable evidence, repeated data entry, incomplete records, traceability and the quality of technician-confirmed outcomes.