Data Optimization
FlexConnect Service & Data Optimization

Introduction
This guide outlines the implementation of FlexConnect to ensure a high-performance telemetry system while maintaining cost control. By leveraging the system’s modular architecture, organizations can fine-tune data resolution against budgetary requirements.
To achieve the ideal balance between data visibility and operational expenditure, Audesse recommends a tiered approach to configuration. While parameters like Fleet Size and Service Hours are typically fixed by your operations, the following technical levers allow for significant optimization of both the Data Source Layer and your Monthly Base Fees.
Optimization Priority 1: Upload Delay (The “Liveness” Factor)
The most impactful way to reduce costs without sacrificing data resolution is to increase the Upload Delay.
- How it Works: By extending the delay, the edge device buffers and compresses data into larger, more efficient batches using gzip.
- The Benefit: Sending one large data packet instead of many small ones reduces the protocol overhead at the Ingestion Layer.
- Recommendation: If real-time “live” viewing (e.g., <30 seconds) is not mission-critical, set this to the maximum permissible value. You retain 100% of your data resolution while lowering transmission costs.
Optimization Priority 2: Per-Signal Sample Period
If data volume remains high, the next step is to evaluate the frequency of measurement at the Data Source Layer.
- Dynamic Configuration: FlexConnect allows you to set the sample period individually for every signal.
- Low-Velocity Signals: For metrics that change slowly (e.g., fuel level, ambient temperature, or daily odometer), increase the sample period to the highest possible interval.
- High-Velocity Signals: Reserve high-resolution sampling (low period) only for active tracking needs, such as motor RPM or critical safety sensors.
Optimization Priority 3: Signal Pruning
The final optimization tier is the reduction of the total Number of Signals being transmitted to the Storage Layer.
- Audit Your Data: Review your dashboard and remove any CAN signals that are not actively used for diagnostics, alerts, or reporting.
- Direct Impact: Each removed signal directly reduces the processing load on the Ingestion Layer and the storage footprint in the TSDB.
Implementation Tools & Management
Audesse provides integrated tools to manage these configurations seamlessly without requiring complex manual coding:
- DBC Upload Tool: Use this via the Audesse dashboard control panel to instantly configure which signals are recorded and their specific sample rates.
- Granular Control: All parameters can be configured on a per-vehicle basis, allowing you to run high-resolution monitoring on pilot vehicles while maintaining a “low-data” profile for the rest of the fleet.
- Secure Deployment: Once configured, these settings are pushed to the Data Source Layer using the device’s unique encrypted credentials.
Summary of Optimization Impact
| Parameter | Impact on Cost | Impact on Data Quality | Recommended Action |
|---|---|---|---|
| Upload Delay | High | None (only affects latency) | Maximize if “live” data isn’t required. |
| Sample Period | Medium | High (reduces resolution) | Increase for slow-changing variables. |
| Signal Count | Medium | Medium (reduces scope) | Remove non-essential CAN signals. |
FlexConnect Configuration Template
Bellow are some suggested configurations to begin the optimization process.
Tiered Data Profiles
Select a profile based on the vehicle’s role in your fleet to automatically apply optimization logic.
| Profile Tier | Upload Delay (Latency) | Sample Period (Resolution) | Signal Strategy |
|---|---|---|---|
| High-Res (R&D) | Minimal (e.g., 10s) | Fast (e.g., 100ms) | All available CAN signals. |
| Standard (Fleet) | Moderate (e.g., 5m) | Balanced (e.g., 1s) | Critical performance & safety only. |
| Economic (Archival) | Maximum (e.g., 10m+) | Slow (e.g., 10s – 1m) | High-level status & odometer only. |
Signal-Specific Configuration
Use this sample table to map individual signals to their required resolution before uploading via the DBC Tool.
| Signal Name | Priority (High/Med/Low) | Sample Period (ms/s) | Justification |
|---|---|---|---|
| e.g., Battery Voltage | Medium | 1s | Monitor health without bloating data. |
| e.g., Motor RPM | High | 100ms | Required for performance analysis. |
| e.g., Fuel Level | Low | 10s | Changes slowly; low resolution suffice. |
| e.g., Ambient Temp | Low | 1m | Environmental baseline only. |