![]() However, look at the duration figures: "3d 6h" to cook, yet it is finished on the second day? That is the effort conversion factors making their presence known. The chef comes in on the first day, preps the food, throws it in the slow cooker, where it stews for a bit more than 1 full day, and it is ready to eat in the latter part of the second day. That's looking a little more like it (though the durations are much longer than any slow cooker recipe I've encountered). Here's how it looks after I set the project schedule to also be 24x7: You've set your slow cooker resource's schedule to be 24x7, but that doesn't have any effect because the project schedule is more restrictive. In your sample file, you've got project working hours of M-F 8-5. For example, a busy factory might run production in 3 8 hour shifts each day, 6 days a week, but an individual worker would have a resource schedule that only assigned them to 1 shift per day. Individual resources may have a schedule which restricts them to a subset of the project working hours. The project schedule (set up in View->Calendar View or the calendar view tab) gives the working hours for the project. Project and resource schedules tell OmniPlan which hours it can use to schedule activities. Effort conversion factors apply to the entire project, and are set in the Project : Unit Conversions inspector. There are a number of factors in play here:Įffort conversion factors are the numbers OmniPlan uses to convert the units we use (minutes, hours, days, weeks, months, years) into the units it uses (seconds).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |