Hours of Service constraints are checked during pairing (or when the requested start date time/requested end date time changes) to help you avoid overscheduling a worker.

Hours of Service constraints are configured per operation. Multiple constraints can be configured.

Logistics Execution > Setup > Constraints > Hours of Service Constraints

• Operation – Operation for the Hours of Service Constraint
• Worker Logistics Type – Logistics Type for the Worker Type being calculated
• Task Specific – Controls whether the constraint is against a specific task. If so, the Hours of Service Task must be specified
• Hours of Service Task – Specifies the Hours of Service task to validate against if Constraint is Task Specific.
• Hour Period (Button) – Determines how many hours are applied to the constraint. The following options are available:
  • Custom – The user may change the Hour Period field to any Integer
  • Day – Populates the Hour Period field to 24
  • Week – Populates the Hour Period field to 168
  • Month – Populates the Hour Period field to 720
• Hour Period – Specifies the number of hours this Constraint calculates over
• Maximum Hours – Maximum number of hours of work (or for the specific Hours of Service Task) that can accumulate over the current Hour Period before validation fails during Activity validation
• Warn Hours – Maximum number of hours of work (or for the specific Hours of Service Task) that can accumulate over the current Hour Period before a warning is given during Activity validation
• Hours of Service Constraint Text – Text description of how a particular Hours of Service Constraint will calculate

Pairing _ Validation0

During Pairing or Activity Validation (depending on when Requested Date/Time fields are filled/changed), Hours of Service Constraints are checked. If a constraint fails, the user is notified about the situation. If the warning level is reached, a message is given, but Pairing continues. If the Maximum level is reached, Pairing of the worker will not complete.