> ## Documentation Index
> Fetch the complete documentation index at: https://docs.solvice.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Resource Management

> Configure vehicles, drivers, and teams with advanced constraints and optimization

# Resource Management

Resources represent the vehicles, drivers, or teams that execute your routes. This guide covers advanced resource configuration including multi-shift scheduling, workload balancing, period constraints, and geographic restrictions.

## Basic Resource Configuration

Every resource requires at minimum a name and shift definition:

```json theme={null}
{
  "resources": [
    {
      "id": "driver-1",
      "name": "Driver 1",
      "shifts": [
        {
          "id": "shift1",
          "from": "2024-03-15T08:00:00Z",
          "to": "2024-03-15T17:00:00Z"
        }
      ]
    }
  ],
  "jobs": [
    {
      "id": "job1",
      "name": "Example Job"
    }
  ]
}
```

### Essential Resource Properties

<ParamField body="name" type="string" required>
  Unique identifier for the resource
</ParamField>

<ParamField body="shifts" type="array" required>
  Working periods when the resource is available
</ParamField>

<ParamField body="capacity" type="array[integer]">
  Loading capacity in multiple dimensions (e.g., \[weight, volume])
</ParamField>

<ParamField body="tags" type="array[Tag]">
  Skills, certifications, or capabilities
</ParamField>

<ParamField body="regions" type="array[string]">
  Geographic areas where resource can operate
</ParamField>

## Multi-Shift Resources

Resources can work multiple shifts per day or across different days:

```json theme={null}
{
  "resources": [
    {
      "id": "driver-flexible",
      "name": "Flexible Driver",
      "shifts": [
        {
          "id": "shift1",
          "start": {
            "location": {"lat": 52.520, "lon": 13.405},
            "time": "2024-03-15T06:00:00Z"
          },
          "end": {
            "location": {"lat": 52.520, "lon": 13.405},
            "time": "2024-03-15T10:00:00Z"
          }
        },
        {
          "id": "shift2",
          "start": {
            "location": {"lat": 52.520, "lon": 13.405},
            "time": "2024-03-15T14:00:00Z"
          },
          "end": {
            "location": {"lat": 52.525, "lon": 13.410},
            "time": "2024-03-15T18:00:00Z"
          }
        },
        {
          "id": "shift3",
          "start": {
            "location": {"lat": 52.525, "lon": 13.410},
            "time": "2024-03-16T08:00:00Z"
          },
          "end": {
            "location": {"lat": 52.520, "lon": 13.405},
            "time": "2024-03-16T17:00:00Z"
          }
        }
      ]
    }
  ],
  "jobs": [
    {
      "id": "job1",
      "name": "Example Job"
    }
  ]
}
```

<Tip>
  Each shift can have different start/end locations. This is useful for drivers who:

  * Start from home in the morning
  * End at a depot
  * Continue from previous day's end location
</Tip>

### Shift Properties

<ParamField body="from" type="datetime" required>
  Shift start time (ISO 8601 format)
</ParamField>

<ParamField body="to" type="datetime" required>
  Shift end time
</ParamField>

<ParamField body="start" type="Location">
  Starting location for this shift (defaults to first job location)
</ParamField>

<ParamField body="end" type="Location">
  Ending location for this shift (defaults to last job location)
</ParamField>

<ParamField body="overtimeEnd" type="datetime">
  Latest possible end time with overtime penalty
</ParamField>

<ParamField body="breaks" type="array[Break]">
  Scheduled breaks during the shift
</ParamField>

## Period Constraints

Control resource utilization over time periods (day, week, month):

```json theme={null}
{
  "resources": [
    {
      "id": "driver-1",
      "name": "Driver 1",
      "periodRules": [
        {
          "type": "MAX_WORK_TIME",
          "period": "DAY",
          "value": 28800  // 8 hours max per day
        },
        {
          "type": "MAX_DRIVE_TIME",
          "period": "WEEK",
          "value": 144000  // 40 hours max per week
        },
        {
          "type": "MIN_SERVICE_TIME",
          "period": "DAY",
          "value": 14400  // Minimum 4 hours productive work
        }
      ],
      "shifts": [
        {
          "id": "shift1",
          "from": "2024-03-15T08:00:00Z",
          "to": "2024-03-15T17:00:00Z"
        }
      ]
    }
  ],
  "jobs": [
    {
      "id": "job1",
      "name": "Example Job"
    }
  ]
}
```

### Available Period Rules

<Tabs>
  <Tab title="Work Time Limits">
    ```json theme={null}
    {
      "type": "MAX_WORK_TIME",
      "period": "DAY",
      "value": 32400  // 9 hours
    }
    ```

    Total time from shift start to end, including breaks
  </Tab>

  <Tab title="Drive Time Limits">
    ```json theme={null}
    {
      "type": "MAX_DRIVE_TIME",
      "period": "WEEK",
      "value": 144000  // 40 hours
    }
    ```

    Actual driving/travel time only
  </Tab>

  <Tab title="Service Time Requirements">
    ```json theme={null}
    {
      "type": "MIN_SERVICE_TIME",
      "period": "DAY",
      "value": 21600  // 6 hours minimum
    }
    ```

    Productive time spent at job locations
  </Tab>
</Tabs>

<Info>
  **Period Types:**

  * `DAY`: Rolling 24-hour period
  * `WEEK`: Rolling 7-day period
  * `MONTH`: Rolling 30-day period
</Info>

## Workload Balancing

Distribute work fairly across resources:

### Fair Workload Per Resource

Balance total work time across all resources:

```json theme={null}
{
  "options": {
    "weights": {
      "fairWorkloadPerResource": 50
    }
  }
}
```

**How it works:**

* Calculates average workload across all resources
* Penalizes deviations from the average
* Higher weight = stronger preference for balance

<CodeGroup>
  ```json Balanced Distribution theme={null}
  // With fairWorkloadPerResource: 100
  {
    "resource1": "6 hours work",
    "resource2": "6.5 hours work",
    "resource3": "5.5 hours work"
  }
  ```

  ```json Unbalanced Distribution theme={null}
  // With fairWorkloadPerResource: 0
  {
    "resource1": "9 hours work",
    "resource2": "3 hours work",
    "resource3": "4 hours work"
  }
  ```
</CodeGroup>

### Fair Workload Per Trip

Balance work within individual trips/routes:

```json theme={null}
{
  "options": {
    "weights": {
      "fairWorkloadPerTrip": 30
    }
  }
}
```

**Use cases:**

* Ensure lunch breaks fall at reasonable times
* Prevent very short or very long individual routes
* Balance morning vs afternoon workloads

## Geographic Restrictions

### Region-Based Assignment

Limit resources to specific geographic areas:

```json theme={null}
{
  "resources": [
    {
      "id": "north-team",
      "name": "North Team",
      "regions": ["region-north", "region-central"],
      "shifts": [
        {
          "id": "shift1",
          "from": "2024-03-15T08:00:00Z",
          "to": "2024-03-15T17:00:00Z"
        }
      ]
    },
    {
      "id": "south-team",
      "name": "South Team", 
      "regions": ["region-south", "region-central"],
      "shifts": [
        {
          "id": "shift1",
          "from": "2024-03-15T08:00:00Z",
          "to": "2024-03-15T17:00:00Z"
        }
      ]
    }
  ],
  "jobs": [
    {
      "id": "delivery-1",
      "name": "Delivery 1",
      "location": {"lat": 52.520, "lon": 13.405},
      "region": "region-north"
    }
  ]
}
```

<Warning>
  Jobs with regions can ONLY be assigned to resources that include that region in their regions list.
</Warning>

### Distance-Based Restrictions

Limit how far resources travel from their base:

```json theme={null}
{
  "resources": [
    {
      "id": "local-driver",
      "name": "Local Driver",
      "shifts": [{
        "id": "shift1",
        "from": "2024-03-15T08:00:00Z",
        "to": "2024-03-15T17:00:00Z",
        "maxDistance": 50000  // 50km radius from start
      }]
    }
  ],
  "jobs": [
    {
      "id": "job1",
      "name": "Example Job"
    }
  ]
}
```

## Skill and Tag Management

Match resource capabilities with job requirements:

```json theme={null}
{
  "resources": [
    {
      "id": "certified-technician",
      "name": "Certified Technician",
      "tags": [
        {"name": "electrical", "hard": true},
        {"name": "plumbing", "hard": true},
        {"name": "senior", "hard": false}
      ],
      "shifts": [
        {
          "id": "shift1",
          "from": "2024-03-15T08:00:00Z",
          "to": "2024-03-15T17:00:00Z"
        }
      ]
    }
  ],
  "jobs": [
    {
      "id": "electrical-repair",
      "name": "Electrical Repair",
      "tags": [
        {"name": "electrical", "hard": true}  // Must match
      ]
    }
  ]
}
```

### Tag Matching Rules

<Steps>
  <Step title="Hard Tags Must Match">
    If a job has a hard tag, only resources with that tag can be assigned
  </Step>

  <Step title="Soft Tags Preferred">
    Soft tags create preference but aren't required
  </Step>

  <Step title="Weight Controls Strength">
    Higher weight values make soft preferences stronger
  </Step>
</Steps>

## Preferred Resources

Allow soft preferences for specific resource assignments:

```json theme={null}
{
  "resources": [
    {
      "id": "senior-tech-1",
      "name": "Senior Technician 1",
      "shifts": [{"id": "shift1", "from": "2024-03-15T08:00:00Z", "to": "2024-03-15T17:00:00Z"}]
    },
    {
      "id": "senior-tech-2",
      "name": "Senior Technician 2",
      "shifts": [{"id": "shift1", "from": "2024-03-15T08:00:00Z", "to": "2024-03-15T17:00:00Z"}]
    }
  ],
  "jobs": [
    {
      "id": "vip-customer-service",
      "name": "VIP Customer Service",
      "preferredResources": ["senior-tech-1", "senior-tech-2"],
      "allowedResources": ["senior-tech-1", "senior-tech-2", "tech-3", "tech-4"]
    }
  ],
  "options": {
    "weights": {
      "preferredResourceWeight": 100
    }
  }
}
```

<Info>
  **Resource Assignment Priority:**

  1. `allowedResources` - Hard constraint (if specified)
  2. `preferredResources` - Soft preference with penalty
  3. Tag matching - Based on hard/soft tags
  4. General pool - Any available resource
</Info>

## Complex Example: Field Service Team

Here's a comprehensive example combining multiple resource features:

```json theme={null}
{
  "resources": [
    {
      "id": "senior-tech-north",
      "name": "Senior Technician North",
      "category": "TECHNICIAN",
      "tags": [
        {"name": "electrical", "hard": true},
        {"name": "plumbing", "hard": true},
        {"name": "senior", "hard": true}
      ],
      "regions": ["north", "central"],
      "capacity": [50],  // Tool weight limit
      "shifts": [
        {
          "id": "morning-shift",
          "start": {
            "location": {"lat": 52.540, "lon": 13.420},
            "time": "2024-03-15T07:00:00Z"
          },
          "end": {
            "location": {"lat": 52.540, "lon": 13.420},
            "time": "2024-03-15T12:00:00Z"
          }
        },
        {
          "id": "afternoon-shift",
          "start": {
            "location": {"lat": 52.540, "lon": 13.420},
            "time": "2024-03-15T13:00:00Z"
          },
          "end": {
            "location": {"lat": 52.540, "lon": 13.420},
            "time": "2024-03-15T17:00:00Z"
          },
          "overtimeEnd": "2024-03-15T19:00:00Z"
        }
      ],
      "periodRules": [
        {
          "type": "MAX_WORK_TIME",
          "period": "DAY",
          "value": 36000  // 10 hours max
        },
        {
          "type": "MAX_DRIVE_TIME",
          "period": "WEEK",
          "value": 108000  // 30 hours driving per week
        }
      ]
    },
    {
      "id": "junior-tech-south",
      "name": "Junior Technician South",
      "category": "TECHNICIAN",
      "tags": [
        {"name": "electrical", "hard": true},
        {"name": "junior", "hard": true}
      ],
      "regions": ["south", "central"],
      "capacity": [30],
      "shifts": [
        {
          "id": "full-day",
          "start": {
            "location": {"lat": 52.540, "lon": 13.420},
            "time": "2024-03-15T08:00:00Z"
          },
          "end": {
            "location": {"lat": 52.540, "lon": 13.420},
            "time": "2024-03-15T17:00:00Z"
          },
          "breaks": [
            {
              "type": "FIXED",
              "from": "2024-03-15T12:00:00Z",
              "to": "2024-03-15T13:00:00Z"
            }
          ]
        }
      ]
    },
    {
      "id": "contractor-flex",
      "name": "Flexible Contractor",
      "category": "CONTRACTOR",
      "tags": [
        {"name": "electrical", "hard": true},
        {"name": "contractor", "hard": true}
      ],
      "regions": ["north", "south", "central"],
      "capacity": [40],
      "shifts": [
        {
          "id": "contractor-shift",
          "from": "2024-03-15T10:00:00Z",
          "to": "2024-03-15T18:00:00Z"
        }
      ],
      "hourlyCost": 75  // Higher cost for contractors
    }
  ],
  "jobs": [
    {
      "id": "job1",
      "name": "Example Job"
    }
  ],
  "options": {
    "weights": {
      "fairWorkloadPerResource": 50,
      "preferredResourceWeight": 100,
      "overtimeWeight": 200
    }
  }
}
```

## Performance Optimization

### Resource Pool Size

<Warning>
  **Performance Impact of Resource Features:**

  * More resources = more routing possibilities
  * Complex constraints = longer solve times
  * Many tags/regions = increased matching complexity

  **Recommendations:**

  * Keep active resource pool under 100 for real-time solving
  * Use shift patterns to reduce combinations
  * Limit tag variations to necessary distinctions
</Warning>

### Best Practices

<Steps>
  <Step title="Start Simple">
    Begin with basic resource definitions and add constraints incrementally
  </Step>

  <Step title="Use Appropriate Constraints">
    * Hard constraints for legal/safety requirements
    * Soft constraints for preferences
    * Period rules for compliance
  </Step>

  <Step title="Test Resource Utilization">
    Monitor these metrics:

    * Average utilization per resource
    * Overtime frequency
    * Unassigned jobs due to resource constraints
  </Step>

  <Step title="Balance Flexibility and Control">
    Too many restrictions can make problems infeasible
  </Step>
</Steps>

## Troubleshooting

### Common Issues

<AccordionGroup>
  <Accordion title="Jobs Not Assigned to Preferred Resources">
    **Possible Causes:**

    * Preferred resource doesn't have required tags
    * Resource shift doesn't cover job time window
    * Capacity constraints prevent assignment
    * Travel time makes assignment inefficient

    **Solutions:**

    * Verify resource has all required capabilities
    * Check shift coverage and time windows
    * Increase preferredResourceWeight
    * Review overall constraint interactions
  </Accordion>

  <Accordion title="Uneven Workload Distribution">
    **Possible Causes:**

    * Geographic clustering of jobs
    * Skill requirements limiting options
    * Time window constraints
    * Different shift lengths

    **Solutions:**

    * Increase fairWorkloadPerResource weight
    * Adjust shift patterns for better coverage
    * Consider redistributing regions
    * Add more flexible resources
  </Accordion>

  <Accordion title="Period Constraints Violated">
    **Possible Causes:**

    * Constraints too restrictive
    * Not enough resources for workload
    * Poor shift distribution

    **Solutions:**

    * Review and adjust period rule values
    * Add additional resources or shifts
    * Enable partial planning
    * Distribute work across more days
  </Accordion>
</AccordionGroup>

## Related Features

<CardGroup cols={2}>
  <Card title="Time Scheduling" icon="calendar" href="/guides/vrp/features/time-scheduling-advanced">
    Detailed shift configuration and time management
  </Card>

  <Card title="Cost Optimization" icon="dollar-sign" href="/guides/vrp/features/cost-optimization">
    Resource costs and optimization strategies
  </Card>

  <Card title="Tag System" icon="tags" href="/guides/vrp/features/tag-ranking">
    Advanced tag matching and ranking
  </Card>

  <Card title="Break Management" icon="coffee" href="/guides/vrp/features/break-management">
    Configure breaks within shifts
  </Card>
</CardGroup>