you wrote that bad weather happened during execution.
It means that entering actual data you shall exclude from the input table those activities that were not executed in report period or enter smaller actual volumes and actual work hours if activity execution was slower than planned.
Performance interruptions do not create new links (logical dependencies) with other activities.
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Fri, 2019-07-12 12:35
Apply the exception to the calendar(s) of impacted activities. If the calendar is shared among impacted and non impacted activities create as many calendars are necessary to keep them apart. Easy if using copy-paste.
Spider allows for an alternate method based on rain hours rather than rain days as follows: We don't know when the rains (or snow, or extreme cold) may happen. - Based on expected weather we can define 24/7 work weeks with different work minutes per hour. Then we set calendar exceptions as to apply the right week to different periods of our Rain Calendar. We apply the work calendar to the activity and a Rain Resource with the Rain Calendar. As a forward looking method I find it better but harder to maintain because all exceptions applied to what we now know no rain happened must be erased.
At home rain days approach is what is required and this I follow in my schedule submittals. For short term management I keep a separate optimistic version I update the schedule recording rain days as they happened but assume no rain days in the future. Imagine I had a "planned" rain day and it does not happens, such plan will artificially delay some activities.
Member for
24 years 9 monthsMarian,you wrote that bad
Marian,
you wrote that bad weather happened during execution.
It means that entering actual data you shall exclude from the input table those activities that were not executed in report period or enter smaller actual volumes and actual work hours if activity execution was slower than planned.
Performance interruptions do not create new links (logical dependencies) with other activities.
Member for
21 years 8 monthsCreate a calendar
Planning and Accounting for Adverse Weather - 84R-13
Planning for adverse weather in Construction Projects
Spider allows for an alternate method based on rain hours rather than rain days as follows: We don't know when the rains (or snow, or extreme cold) may happen. - Based on expected weather we can define 24/7 work weeks with different work minutes per hour. Then we set calendar exceptions as to apply the right week to different periods of our Rain Calendar. We apply the work calendar to the activity and a Rain Resource with the Rain Calendar. As a forward looking method I find it better but harder to maintain because all exceptions applied to what we now know no rain happened must be erased.
At home rain days approach is what is required and this I follow in my schedule submittals. For short term management I keep a separate optimistic version I update the schedule recording rain days as they happened but assume no rain days in the future. Imagine I had a "planned" rain day and it does not happens, such plan will artificially delay some activities.