Home›Products›Engineering›Product Builder
Engineering · Product Builder

Build products. Deploy in minutes.

Compose products from CAN signals, DTCs, and OEM PIDs. Deploy to gateway firmware in minutes — not weeks. Versioned, validated, and QA-tested per device class before rollout.

How It Works

Compose. Validate. Deploy. Iterate.

1

Compose

Pick CAN signals from any DBC. Reference DTCs from the 100K+ library. Map OEM-specific PIDs.

2

Validate

Schema-checked JSON product definitions. Conflicts and missing dependencies flagged before save.

3

QA

QA configs per device class. Test on a benchtop FleetConnect with a recorded trace, not in production.

4

Deploy

Push via SafeSync OTA to a single device, a fleet, or a staged rollout cohort. Auto-rollback on failure.

Sample Product Definition

A Class-8 diesel telematics product, in JSON.

{
  "product": "diesel-class-8-v3",
  "version": "3.4.1",
  "hardware": "FC-501",
  "signals": [
    // J1939 standard PGNs
    { "pgn": 65262, "spns": [110, 174, 175] },
    { "pgn": 61444, "spns": [190, 512, 513] },
    // Cummins-specific extension
    { "pgn": 65265, "oem": "cummins", "spns": [5466] }
  ],
  "dtc_filters": [
    { "dm": 1, "severity": "active" },
    { "dm": 4, "capture_freeze_frame": true }
  ],
  "sample_rates": {
    "position": "1Hz",
    "engine": "5Hz",
    "diagnostics": "event-driven"
  },
  "qa_config": "qa-bench-class-8.yaml"
}

Same workbench as Wayne.

Every product you compose feeds the same data model Wayne reasons over. New signal in the product → new context Wayne can answer about. No second integration.

← Back to Engineering Suite REST API →