The selected operation will be moved to the specified date and the rest of the operations within the specified period will be replanned.

Specify the date by using the dialog shown below.

Example parameter configuration

The three horizons can be specified in hours, days(d) or weeks(w). If no unit is specified, hours are assumed.

Parameter descriptions

(* = configuration required)

Specify how long time backwards from now, from where operations can be replanned.

If set to true, the planHorizon will be calculated from the selected date.
If set to false, the planHorizon will be calculated from now.

If set to true, operations which are to be moved will be placed so they’ll be overlapping possible locked operations.
If set to false, they’ll be placed just after possible locked operations.

Operations with status COMPLETED or with a state from the ignoreStates list, are considered locked.

Here a comma separated list of states can be specified. Thus operations with a status from the list will not be moved. The selected operation will always be moved.

10 = Incomplete
15 = Reserved
20 = Planned
30 = Start possible
40 = Started
50 = Paused
60 = Cancelled
70 = Completed

If set to true, operation before NOW will also be replanned – according to the horizonBeforeNow parameter.
If set to false, operations before NOW will not be replanned.

planHorizon *
Specify how long time ahead operations can be replanned.
The horizon can be calculated from NOW or from the selected date. See parameter horizonStartAtSelectedDate.

In case the selected operation is moved backwards, the pullInHorizon is used to specify how long time ahead from NOW operations can be “pulled in” to avoid unburdened gaps on the resource.

replanningType *

  • ForwardScheduling – respect constraints to previous operations in the route but not successive operations. Sequence of operations may change, however operations before time NOW will be prioritized ahead of operations after time NOW.
  • RawSequence – will not respect constraints to either predecessors or successors in the route. Existing sequence will be respected, operations before time NOW will be placed ahead of operations after time NOW.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment