Here’s a thought. Create two numeric custom data items. First is StdDur (Standard Duration), other is RainDur (Rainy Season Duration). Use Global Change to load all the current OrigDur values into StdDur (so you don’t lose them). Then use Global Change again to load StdDur*1.3 into RainDur. Now - backup the project so you don’t mess it up. Use Global Change to say IF ES is within the rainy season - then OrigDur=RainDur else OrigDur=StdDur. You can make more complex if the IF part to also check EF, etc (dependent upon your comfort with Global Change). You can constantly re-run the Global Change on variations updates to your schedule. You’ll want to make sure you have properly baselined your target so you don’t lose what your original plan was. Can also do something similar to adjust manhours or manpower (whichever you use for manpower reports) - have to make a similar set of custom data-items. Hope that helps, T

Paula

Not sure that you can use a "productivity factor" against either resources or activities. My initial suggestion would be to play around with the limits setting it to 30% and extending the durations to suit.

Someone else out there in cyberworld may know of a better solution. Previously, in a similar situation, I have just extended the durations accordingly. This was done manually and as things slipped had to be re-done as the activities ’moved’ into normal working. Have you tried using a resource calendar?

Nige