Resource Period Rules
Period rules enforce time-based constraints on resources over extended periods, ensuring compliance with labor laws, safety regulations, and operational policies. This guide covers daily, weekly, and monthly limits for work time, drive time, and service time.Period Rule Configuration
Define rules within each resource:Rule Types
Work Time Rules
Total time from shift start to end:Drive Time Rules
Actual time spent driving/traveling:Service Time Rules
Productive time at job locations:Service Time = Time spent performing jobs (excludes travel and breaks)
Period Types
DAY Period
Rolling 24-hour window from current time:1
Calculation
Looks back 24 hours from job start time
2
Example
Job at 14:00 on Tuesday checks work from 14:00 Monday
3
Use Case
Daily driving limits, fatigue management
WEEK Period
Rolling 7-day window:1
Calculation
Looks back 168 hours (7 × 24) from job start
2
Example
Job on Friday checks total work since previous Friday
3
Use Case
Weekly hour limits, EU drivers’ hours rules
MONTH Period
Rolling 30-day window:1
Calculation
Looks back 720 hours (30 × 24) from job start
2
Example
Job on March 15 checks work since February 13
3
Use Case
Monthly quotas, long-term fatigue management
Legal Compliance Examples
EU Drivers’ Hours
US DOT Hours of Service
Soft vs Hard Enforcement
Hard Limits (Default)
Jobs cannot be assigned if they would violate rules:Soft Limits
Allow violations with penalties:Complex Scenarios
Multi-Role Resources
Different rules for different activities:Quota Management
Minimum service requirements:Monitoring and Reporting
Period Rule Status
Track rule compliance in solutions:Best Practices
1
Start Conservative
Set limits slightly below legal requirements for buffer
2
Consider Patterns
Account for typical work patterns and peak periods
3
Use Multiple Rules
Combine daily and weekly limits for comprehensive control
4
Monitor Utilization
Track how close resources get to limits
5
Plan Ahead
Consider future shifts when near limits
Troubleshooting
Jobs Not Assigned Due to Period Rules
Jobs Not Assigned Due to Period Rules
Symptoms: Unassigned jobs with “PERIOD_RULE_VIOLATION” reasonCheck:
- Current period usage for resources
- Rule values vs job requirements
- Hard vs soft rule configuration
- Add more resources
- Adjust shift patterns
- Convert to soft rules if appropriate
Unexpected Rule Violations
Unexpected Rule Violations
Symptoms: Rules violated despite seeming availabilityCheck:
- Rolling window calculations
- Previous days’ work history
- All active rules for resource
- Verify historical data
- Check period window logic
- Review rule combinations
Performance Impact
Performance Impact
Symptoms: Slow solving with period rulesCheck:
- Number of rules per resource
- Historical data lookup time
- Complex rule combinations
- Limit rules to necessary ones
- Use appropriate period types
- Consider caching historical data