Number of hours, for a duration measured in elapsed time.ĮlapsedMinutes ( Number r/o).Number of days, for a duration measured in elapsed time.ĮlapsedHours ( Number r/o).A boolean value that indicates whether or not this duration is measured in project time or elapsed calendar time.ĮlapsedDays ( Number r/o).These can be used to retrieve the time values of duration objects in the desired format.Įlapsed ( Boolean r/o) The default is via project schedule, but scripts can create durations of either type when necessary. A duration is a value that can be measured via the project schedule components or via elapsed time. This same relationship applies to how time is displayed in OmniPlan. The smaller cups may take up more space on the counter but they contain the same amount of Jello as the larger cup - it’s the packaging that is different. To visualize the relationship between the two duration formats (work-time & elapsed-time), imagine you’ve mixed up a pint of Jello®! You can pour the mixture into either three small cups, or into one larger cup. This measure of time is called “elapsed-time” which is a single contiguous amount of time. However, some tasks, such as pouring and setting concrete, by nature require that their process be done in one pass, no matter how many contiguous hours that may require. And it is common for the time it takes to complete a task, to span multiple “work-days” which are comprised of a specified number of “work-hours” per overall day. The length of time required to complete OmniPlan projects is expressed in standard time increments, such as days, weeks, months, and years. The time represented by an instance of the Duration class is organized as either “project time” or “elapsed (contiguous) time.” In terms of OmniPlan projects, a duration is a specified amount of time.

Omniplan set weekends as work days