return to index

Nomadia Field Service API : Chain Constraint Types

Opti-Time Chain Constraint types (APPOINTMENT.CHAINCONSTRAINTKIND)


Appointment chain constraint types
Property Data type Value Description Condition Mode
Not defined Integer 0 Appointment is not typed-link to another one Only CHAINCONSTRAINTORDER, CHAINCONSTRAINTMINDELAY OR CHAINCONSTRAINTMAXDELAY defined on the chain model are used and values on each appointment are used
Spacing (and ordering) Integer 1 Appointments linked are time-spaced (unit=days / 0=same days / 1=day and day after / 2=one day interleaved...)

Number of day is defined by CHAINCONSTRAINTMINDELAY or CHAINCONSTRAINTMAXDELAY (NOT BOTH), Ordering may be defined with CHAINCONSTRAINTORDER		 Constraints have to be compatible each others
Same resource Integer 2 Appointments linked have to be planned to same resource

 Resources have to be able to do these appointments (resources priorities/skills/jobs/worked-days/distances...).
Obviously inconsistent if combined with "Same Start"
Grouped : The maximum spacing relates to the first appointment Integer 8 Appointments linked cannot be spaced more than N days from the first appointment of the chain

Number of day is defined by CHAINCONSTRAINTMAXDELAY		 The maximum space between days is defined in DAY unit
Appointments planned are into the time scope of the scheduling process used
Some appointments may not to be planned
Grouped + Same resource Integer 10 Combine constraint Same Resource (2) with constraint "grouped" (8, maximum spacing relates to first)
Value 10=8+2
 The resource have to be able to do these appointments (resource priority/skill/job/worked-days/distance...)
Delayed : The minimum spacing relates to the first appointment Integer 16 Appointments linked cannot be spaced less than N days from the first appointment of the chain

Number of day is defined by CHAINCONSTRAINTMINDELAY		 The minimum space between days is defined in DAY unit
Appointments planned are into the time scope of the scheduling process used
Some appointments may not to be planned
Delayed + Same resource Integer 18 Combine constraint Same Resource (2) with constraint "Delayed" (18, minimum spacing relates to first)
Value 10=8+2
 The resource have to be able to do these appointments (resource priority/skill/job/worked-days/distance...)
Same start Integer 32 Appointments linked must start the same day at same time (even if they have distinct duration and requirements) Obviously inconsistent if combined with "Same Resource"
Distinct days Integer 256 Appointments linked cannot be planned the same day

 The minimum space between days is defined to 1

Some appointments may not to be planned
Ordered Tour Integer 514 Appointments linked have to be done the same day, by the same resource
Value 514=; CHAINCONSTRAINTORDER field have to be defined and managed		 Some appointments may not to be planned if there is not enough time into the worked day
Ordered Circuit Integer 518 Appointments linked have to be done the same day, by the same resource, one by one without any other appointment inserted into the chain
Value 518=; CHAINCONSTRAINTORDER field have to be defined and managed		 Some appointments may not to be planned if there is not enough time into the worked day Dispatcher formulae doesn't works every time
Circuit Integer 14 Appointments linked have to be done by the same resource, one by one without any other appointment inserted into the chain
Value 14=2+4+8 with Space between appointments forced to 0 days; CHAINCONSTRAINTORDER field is managed		 Some appointments may not to be planned if there is not enough time into the worked day ONLY with RealTime Optimization Engine
Stappling Integer 1030 Appointments linked have to be done on many days, by the same resource, one by one without any other appointment inserted into the chain
CHAINCONSTRAINTORDER is managed
All or none appointment are planned		 Appoinments have same location, same resource, no ordering
The system considers appointments as ONE long appointment, plan it virtualy and then put each link subsequently without any other constraint
All or none appointments of each chain are planned		 ONLY with RealTime Optimization Engine

Note : To manage that kind of constraint in batch Optimization, using advanced heuristics like "Filling by Visits H6" or "Addition by Sector H9" appears to be more efficient than the default "High" heuristic ("Filling by route H5").
return to index