![]() ![]() Why did entering “2d” for duration turn into 4 days of calendar delay when scheduled over a weekend? Well, duration always calculates the interval according to the project schedule: when you enter 2d, it’s going to advance the project schedule 2 days from the start date: so if the task is dependent on a task that finishes at the end of the work day on Thursday, 2 days later on the work calendar will be the end of the day on the following Monday, which is of course 4 calendar days later. You can make this a little less confusing by always displaying effort in hours, rather than using weeks or days: in the Project inspector, the Formats section has checkboxes for which units it should use when displaying Duration and Effort. This means means that “48 hours” of effort will be displayed by OmniPlan as 1 week (40 hours) + 1 day (8 hours) of effort. In the Project inspector, under Effort Unit Conversion, you can see that (by default) 1 work day is defined to be 8 hours and 1 work week is defined to be 40 hours. Your “wait” resource is able to work 24 hours a day. Is that what you were looking to accomplish? ![]() Short answer: try giving the task an effort of “48h”. ![]() However, if I give the task a duration of 2 days, I end up with an effort of over a week … and the task will still show up as 4 days on the calendar if it spans a weekend. Because the resource works 24 hours a day, 7 days a week, and is assigned 100% to the project, I expect the “effort” and “duration” for these tasks to be identical. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |