buildingSMART / buildingSMART/IFC4.x-development
Introduce an attribute to IfcWorkSchedule that defines by which calendar is IfcRelSequence LagValue calculated
Open
allocated-sequence
ifc-update-out
proposal
- Dominant language
- Python
- Stars
- 234
- Forks
- 123
- Avg merge
- 15h 4m
- Merged PRs (30d)
- 5
Description
If the TimeLag attribute of the IfcRelSequence entity is set to be worktime (IfcTaskDurationEnum.WORKTIME) it's not clear by which calendar the task relation lag should be calculated.
In order to specify which calendar is used for task relation lag calculation, it's necessary to introduce a new enum attribute to the IfcWorkSchedule that has the following values:
• PredecessorTaskCalendar
• SuccessorTaskCalendar
• ScheduleDefaultCalendar
This way it would be absolutely clear which calendar should be used for task relation lag calculation.
Contributor guide
Assessment
This issue has not been assessed yet.