How to schedule un -splittable tasks

Thanks Vladimir, it is way easier but perhaps only available for Spider users. Now this approach is on my list of Spider scheduling strategies.

  In this example I used a Calendar Exception named "Shut Down" and an activity interruption of no more than .001 hours.

  In this example I used a Calendar Exception named "Shut Down" but not the prerformance interruption restriction.

Both yields different results, choose the one/combination that best meets your requirements.

Thank you Rafael,

we'll change this in the new version.

Vladimir, perhaps it could help if istead of "allow performance interruptions ..." it reads "restrict performance interruptions ..." as to make it easier to find the parameter code/name for reports.

Yes Rafael, you are right, this is Spider Project option like many others absent in other tools.

Alexanre,

in Spider Project you can set that activity interruption is allowed for not more than N days.

In this case such activities will be automatically delayed to the next "window" if they could not be completed in the current "window".

Non-work calendar time does not split an activity. If an activity calendar is 8 hours per day and it works for five days it does not mean activity is split.

- In this sample schedule we have an availability of 10,000 ea. resources D1 except for the time span shutdown is scheduled where availability is set to 0.

- We use time resource production as to make D1 unavailable during shutdown and assign one unit to each activity that you do not want to stop work during shutdown but to be 100% scheduled before the shutdown or 100% after the shutdown.

- If using Microsoft Project try adjusting units of effort availability under resource information.

Good luck.