Syncing contracts to automate data sharing

Rental businesses often manage hundreds of active contracts with varying equipment assignments, project timelines, and customer requirements. Manual data sharing management becomes inefficient and error-prone at scale. This guide shows how to automate data sharing based on your contract lifecycle.

This approach transforms contract events into automated data sharing actions, ensuring your customers always have the right access to the right equipment data at the right time.

Overview

Contract-driven automation synchronizes your business systems with Hiboo's sharing capabilities, creating a seamless flow from contract signature to automatic data access.

Key Benefits:

• Eliminate manual errors: Automatically create and manage sharings based on contract data

• Improve customer experience: Equipment data becomes available immediately when contracts start

• Scale efficiently: Handle hundreds of simultaneous contracts without manual intervention

• Ensure compliance: Automatically stop data sharing when contracts end or are terminated

Common Integration Sources:

• Rental management systems: Wynne Systems, Point of Rental, Alert EasyPro, RentalMan

• ERP systems: SAP, Oracle, NetSuite, Microsoft Dynamics

• CRM systems: Salesforce, HubSpot, custom customer management systems

• Project management tools: Procore, PlanGrid, custom project systems

Contract Lifecycle Automation

New Contract Activation

Problem: When a rental contract begins, customers need immediate access to their equipment data for project planning and operations monitoring.

Solution: Automatically create data sharings when contracts are activated in your business system.

Implementation approach:

Contract event detection:

1. Monitor your rental system for new active contracts

2. Extract equipment assignments and customer contact information

3. Determine required data packages based on contract type

4. Generate sharing reference using contract identifier

Automated sharing creation:

POST /v2/fleet/sharings
{
  "reference": "CONTRACT-ABC123-2024",
  "startDate": "2024-01-15T00:00:00Z",
  "endDate": "2024-06-30T23:59:59Z",
  "assetIds": [1234, 1235, 1236],
  "recipient": "[email protected]",
  "notificationEnabled": true,
  "properties": {
    "contract": "ABC123",
    "customer": "ABC Construction",
    "site": "Highway Project Phase 2",
    "project": "DOT-2024-015"
  }
}

Key considerations:

• Reference format: Use consistent contract-based references for easy tracking

• Customer contacts: Ensure correct recipient email from your CRM/customer database

• One sharing per asset: Most customers prefer individual sharings for each piece of equipment to simplify updates and machine swaps

Recommended sharing strategy:

// Instead of one sharing with multiple assets
POST /v2/fleet/sharings
{
  "reference": "CONTRACT-ABC123-2024",
  "assetIds": [1234, 1235, 1236]  // Multiple assets
}

// Create individual sharings for easier management
POST /v2/fleet/sharings
{
  "reference": "CONTRACT-ABC123-2024-EXCAVATOR-001",
  "assetIds": [1234],  // Single asset
  "properties": {
    "contract": "ABC123",
    "customer": "ABC Construction", 
    "site": "Highway Project Phase 2",
    "project": "DOT-2024-015"
  }
}

POST /v2/fleet/sharings
{
  "reference": "CONTRACT-ABC123-2024-DOZER-002", 
  "assetIds": [1235],  // Single asset
  "properties": {
    "contract": "ABC123",
    "customer": "ABC Construction",
    "site": "Highway Project Phase 2", 
    "project": "DOT-2024-015"
  }
}

Contract Modifications

Problem: Rental contracts frequently change—equipment additions, removals, timeline extensions, or customer contact updates require data sharing adjustments.

Solution: Automatically update existing sharings when contract modifications occur.

Modification scenarios:

Equipment changes:

// With one asset per sharing, equipment swaps are simple:

// 1. Stop sharing for equipment being returned
DELETE /v2/fleet/sharings/CONTRACT-ABC123-2024-EXCAVATOR-001

// 2. Create sharing for replacement equipment  
POST /v2/fleet/sharings
{
  "reference": "CONTRACT-ABC123-2024-EXCAVATOR-003",
  "startDate": "2024-01-15T00:00:00Z",
  "endDate": "2024-06-30T23:59:59Z", 
  "assetIds": [1237],  // New replacement excavator
  "recipient": "[email protected]",
  "notificationEnabled": true,
  "properties": {
    "contract": "ABC123",
    "customer": "ABC Construction",
    "site": "Highway Project Phase 2",
    "project": "DOT-2024-015"
  }
}

// Other equipment sharings remain unaffected

Benefits of one asset per sharing:

• Simplified swaps: Replace individual machines without affecting other equipment access

• Granular control: Different data packages or access levels per equipment type

• Easier tracking: Clear audit trail for each piece of equipment

• Reduced errors: Lower risk of accidentally affecting wrong equipment during updates

Timeline extensions:

PATCH /v2/fleet/sharings/CONTRACT-ABC123-2024
{
  "endDate": "2024-09-30T23:59:59Z"  // Extended project end date
}

Contact updates:

PATCH /v2/fleet/sharings/CONTRACT-ABC123-2024
{
  "properties": {
    "contract": "ABC123",
    "customer": "ABC Construction",
    "site": "Highway Project Phase 2",
    "project": "DOT-2024-015"
  }
}

Note: Equipment list changes require recreating the sharing as assetIds cannot be modified through PATCH operations.

Contract Completion

Problem: When rental contracts end, data access should be terminated promptly to maintain security and comply with data sharing agreements.

Solution: Automatically stop data sharings when contracts are marked complete or terminated.

Contract completion automation:

1. Detect contract completion in your rental system
2. Stop active data sharing immediately
3. Update contract status tracking

Equipment Management Best Practices

One Asset Per Sharing Strategy

Problem: Equipment swaps, replacements, and reassignments are common in rental operations, but managing multi-asset sharings makes updates complex and error-prone.

Solution: Create individual sharings for each piece of equipment to simplify management and reduce operational overhead.

Single-asset sharing approach:

// Create separate sharings for each piece of equipment
POST /v2/fleet/sharings
{
  "reference": "CONTRACT-ABC123-2024-EXCAVATOR-001",
  "assetIds": [1234],  // Single excavator
  "recipient": "[email protected]",
  "startDate": "2024-01-15T00:00:00Z",
  "endDate": "2024-06-30T23:59:59Z",
  "properties": {
    "contract": "ABC123",
    "customer": "ABC Construction",
    "site": "Highway Project Phase 2"
  }
}

POST /v2/fleet/sharings  
{
  "reference": "CONTRACT-ABC123-2024-DOZER-002",
  "assetIds": [1235],  // Single dozer
  "recipient": "[email protected]", 
  "startDate": "2024-01-15T00:00:00Z",
  "endDate": "2024-06-30T23:59:59Z",
  "properties": {
    "contract": "ABC123",
    "customer": "ABC Construction", 
    "site": "Highway Project Phase 2"
  }
}

Equipment Swaps and Replacements

Equipment replacement workflow:

// When equipment needs replacement:

// 1. Stop sharing for equipment being returned
DELETE /v2/fleet/sharings/CONTRACT-ABC123-2024-EXCAVATOR-001

// 2. Create sharing for replacement equipment
POST /v2/fleet/sharings
{
  "reference": "CONTRACT-ABC123-2024-EXCAVATOR-003",
  "assetIds": [1237],  // Replacement excavator
  "recipient": "[email protected]",
  "startDate": "2024-02-01T00:00:00Z",  // Swap date
  "endDate": "2024-06-30T23:59:59Z",
  "properties": {
    "contract": "ABC123",
    "customer": "ABC Construction",
    "site": "Highway Project Phase 2"
  }
}

// All other equipment sharings remain active and unaffected

Benefits of single-asset sharings:

• Simplified swaps: Replace individual machines without affecting other equipment

• Granular control: Different data packages or contact persons per equipment type

• Clear audit trails: Easy tracking of individual equipment access history

• Reduced errors: Lower risk of accidentally affecting multiple pieces of equipment

• Faster operations: Quick equipment changes without complex asset list management

Implementation Best Practices

Error Handling and Recovery

Contract synchronization resilience:

• Implement retry logic with exponential backoff for API failures

• Maintain synchronization status tracking in your system

• Create alerting for failed contract automation

• Design rollback procedures for partial failures

Data consistency:

• Verify sharing creation success before marking contracts as "data-enabled"

• Implement periodic reconciliation between your system and Hiboo

• Handle edge cases like duplicate contracts or overlapping equipment assignments

• Log all automation actions for audit and troubleshooting