Page 1 of 1

Elapsed duration

Posted: Fri Nov 04, 2016 2:02 pm
by Fer23
We have tasks with elapsed duration in Microsoft Project. How is it handled in RiskyProject?

Re: Elapsed duration

Posted: Fri Nov 04, 2016 2:28 pm
by Intaver Support
Elapsed duration is a feature of Microsoft Project. Elapsed days are used when a task’s duration needs to disregard any ‘nonworking time’ or resource constraints. For example if you need a task to be scheduled over 10 consecutive days including weekends and ignoring resource availability you could set the duration to ‘10 edays’. It is defined by symbol 'e' before duration units, although this symbol can be different for different local versions of Microsoft Project.

Recent version of RiskyProject 6.1 does not support elapsed duration directly, although new version RiskyProject 7 will support it. Currently if Microsoft Project has task duration or lag with elapsed duration RiskyProject calculates equivalent non-elapsed duration based on task start and finish times:


In other words schedule with elapsed duration tasks in RiskyProject will have the same start and finish times for all tasks as in Microsoft Project, but absolute duration of these elapsed duration tasks can be different.