CAN/J1939 Fleet Telemetry Pipeline
Budget: $8 – $15 CAD
NOTE - This is a specialized industrial telemetry integration project and is not a general web development, app development, or IT support engagement. PLEASE CHECK YOUR EXPERIENCE TO THE SCOPE PRIOR TO RESPONDING.
We have an installed heavy-duty telematics unit currently capturing both CAN and J1939 data streams. The remaining requirement is the implementation of a structured cloud-based telemetry environment capable of converting the raw incoming data into organised, validated, and continuously exportable datasets suitable for integration into our AEMS™ analytics stack.
The engagement will begin with the remote commissioning and configuration of the device within a cloud telemetry platform environment. Platform selection remains flexible and may include AWS IoT, Azure IoT, Cloudflare, or comparable infrastructure, depending on the contractor’s recommendation and deployment approach.
The scope of work includes:
Validation of live CAN/J1939 telemetry packets against expected parameter IDs and signal integrity
Structuring and organizing the telemetry environment, including naming conventions, device grouping, access permissions, and data hierarchy
Configuration of reliable export workflows, including API-based exports and scheduled CSV delivery mechanisms, with MQTT capability considered optional for future scalability
Documentation of the full deployment and configuration process to support repeatable rollout across additional assets and fleet deployments
The desired outcome is a stable, scalable, and reproducible telemetry pipeline capable of delivering clean, structured data directly into the ESSNA AEMS™ environment for downstream reporting, analytics, and operational modelling applications without the need for ongoing manual processing.
Contractors with demonstrated experience in industrial telemetry, fleet telematics, CAN/J1939 environments, and cloud-based data integration workflows are encouraged to engage.
We have an installed heavy-duty telematics unit currently capturing both CAN and J1939 data streams. The remaining requirement is the implementation of a structured cloud-based telemetry environment capable of converting the raw incoming data into organised, validated, and continuously exportable datasets suitable for integration into our AEMS™ analytics stack.
The engagement will begin with the remote commissioning and configuration of the device within a cloud telemetry platform environment. Platform selection remains flexible and may include AWS IoT, Azure IoT, Cloudflare, or comparable infrastructure, depending on the contractor’s recommendation and deployment approach.
The scope of work includes:
Validation of live CAN/J1939 telemetry packets against expected parameter IDs and signal integrity
Structuring and organizing the telemetry environment, including naming conventions, device grouping, access permissions, and data hierarchy
Configuration of reliable export workflows, including API-based exports and scheduled CSV delivery mechanisms, with MQTT capability considered optional for future scalability
Documentation of the full deployment and configuration process to support repeatable rollout across additional assets and fleet deployments
The desired outcome is a stable, scalable, and reproducible telemetry pipeline capable of delivering clean, structured data directly into the ESSNA AEMS™ environment for downstream reporting, analytics, and operational modelling applications without the need for ongoing manual processing.
Contractors with demonstrated experience in industrial telemetry, fleet telematics, CAN/J1939 environments, and cloud-based data integration workflows are encouraged to engage.