> For the complete documentation index, see [llms.txt](https://docs.hiboo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hiboo.io/guides/guides/working-with-mixed-fleet-data/cumulative-data-systems.md).

# Exporting cumulative data to your systems

Cumulative counters are essential metrics that track equipment usage over time, providing critical data for maintenance scheduling, cost accounting, and operational analytics. This guide covers the unique challenges and best practices for working with Hiboo's cumulative counter data.

## Overview

Cumulative counters differ from other equipment data because they represent running totals that continuously increase throughout an equipment's operational life. Understanding their behavior and implementing proper handling is crucial for reliable business system integration.

**How Hiboo Simplifies Counter Management:**

* **Standardized counters**: All cumulative data available in consistent formats across equipment brands
* **Business-ready values**: Formatted for direct consumption by enterprise systems

**Unique Counter Characteristics:**

* **Always increasing**: Values should only grow over time (except during resets)
* **Reset scenarios**: Counters may reset to zero during maintenance or component replacement
* **Threshold significance**: Specific counter values trigger business processes

## Understanding Counter Types

### Operating Time Counters

**Cumulative operating hours** track total engine runtime and are fundamental for:

* **Depreciation calculations**: Asset value reduction based on usage
* **Maintenance scheduling**: Service intervals triggered by hour thresholds
* **Rental billing**: Usage-based charging for rental equipment
* **Efficiency analysis**: Comparing operational vs idle time

{% openapi src="<https://spec.hiboo.io/openapiv2.yml>" path="/v2/fleet/equipments/snapshot" method="get" %}
<https://spec.hiboo.io/openapiv2.yml>
{% endopenapi %}

## Counter Reset Scenarios

### Understanding Counter Resets

**Problem**: Equipment counters reset to zero during maintenance, component replacement, or system failures, disrupting business processes that depend on continuously increasing values.

**Solution**: Implement robust reset detection and handling strategies to maintain data continuity for business systems.

**Common reset triggers:**

* **Scheduled maintenance**: Engine overhauls or major component replacement
* **Component failure**: ECU replacement or system malfunctions
* **Software updates**: Firmware updates that clear stored counters
* **Battery disconnection**: Power loss that resets electronic systems

**Reset detection methods:**

**Value decrease detection:**

```
1. Compare current value with previous reading
2. Identify significant decreases (potential resets)
3. Validate against maintenance records
4. Apply appropriate business system update strategy
```

**Maintenance correlation:**

```
1. Cross-reference reset events with maintenance schedules
2. Document reset reason codes for audit trails
3. Maintain continuous usage tracking despite resets
4. Preserve historical data integrity
```

### Business Impact Management

**Problem**: Counter resets can disrupt automated billing, maintenance scheduling, and depreciation calculations.

**Solution**: Implement business logic that maintains operational continuity despite counter resets.

**Continuity strategies:**

* **Virtual counters**: Maintain separate running totals that account for resets
* **Reset adjustment**: Add reset values to subsequent readings
* **Parallel tracking**: Use multiple data sources to validate counter accuracy
* **Business rules**: Define how different systems should handle reset scenarios

**Example reset handling:**

```
Equipment ABC123 counter reset detected:
- Previous reading: 1,247.5 hours
- Current reading: 0.0 hours (reset to zero)
- Business system action: Add 1,247.5 to all future readings
- Maintenance record: Updated with reset event and reason
```

## Threshold-Based Triggers

### Maintenance Scheduling

**Problem**: Business systems need to trigger maintenance actions when equipment counters reach specific thresholds.

**Solution**: Implement threshold monitoring that accounts for counter behavior and business requirements.

{% openapi src="<https://spec.hiboo.io/openapiv2.yml>" path="/v2/fleet/equipments/{id}/{dataKind}" method="get" %}
<https://spec.hiboo.io/openapiv2.yml>
{% endopenapi %}

**Threshold implementation:**

**Service interval triggers:**

```
Operating hours: Trigger maintenance at 250, 500, 1000 hour intervals
Distance milestones: Service alerts at 5,000, 10,000 km intervals
Load cycles: Component inspection after 10,000 cycles
Specialized systems: PTO hours for auxiliary equipment maintenance
```

**Business system integration:**

```
1. Monitor counter progression in real-time
2. Calculate time/usage until next threshold
3. Generate advance warnings for maintenance planning
4. Trigger work orders when thresholds are reached
5. Update maintenance schedules after service completion
```

### Usage-Based Billing

**Problem**: Rental and service agreements require accurate usage tracking for billing purposes.

**Solution**: Implement precise counter monitoring with appropriate validation and billing integration.

**Billing counter applications:**

* **Rental equipment**: Hourly charges based on operating time
* **Service contracts**: Usage-based maintenance pricing
* **Project allocation**: Equipment costs distributed by usage
* **Performance contracts**: Billing based on productivity metrics

**Billing integration considerations:**

```
Reading frequency: Align with billing periods (daily, weekly, monthly)
Validation rules: Ensure counter progression is reasonable
Reset handling: Maintain billing continuity despite counter resets
Audit trails: Document all counter readings for billing disputes
```