OEM Telematics Extension Registry (JD, CIH, CLAAS, AGCO)

The OEM Telematics Extension Registry addresses a critical fragmentation challenge in precision agriculture and off-highway telematics: while ISO 11783 (ISOBUS) and SAE J1939 define baseline CAN protocols, OEMs implement proprietary extensions—including custom PGNs (Parameter Group Numbers), manufacturer-specific DTC definitions, nonstandard scaling, and unique enumeration schemes for operational states (e.g., implement status, hydraulic pressure modes). This registry systematically catalogs those deviations, providing columnar metadata such as OEM name, component/system (e.g., 'Engine', 'Transmission'), parameter name (e.g., 'Active DTC Count'), raw CAN identifier (PGN/SPN or CAN ID), data length, byte/bit position, scaling factor (multiplier), offset (adder), engineering units (e.g., kPa, °C, %), and value enumeration tables (e.g., '0=Off, 1=Auto, 2=Manual'). It supports both static metadata (e.g., sensor calibration constants) and dynamic signal interpretations (e.g., bitmask decoding for multi-state flags). Practically, the registry is used by telematics service providers, OEM-agnostic fleet software developers, and Tier-1 suppliers to normalize incoming CAN logs into unified data models—enabling cross-OEM dashboards, predictive maintenance triggers, and regulatory reporting (e.g., EPA/FCC telematics compliance). Its Excel format facilitates version control, stakeholder collaboration (OEMs, integrators, agtech partners), and integration with ETL pipelines via structured import (e.g., Python pandas parsing with defined schema validation).