IfcEventTime captures the time-related information about an event including the different types of event dates (i.e. actual, scheduled, early, and late).
All given values should be provided by the application, that is, the IFC schema does not deal with dependencies between process time values. At this stage there is also no consistency check through where rules that guarantee a meaningful population of date values. Thus, an application is responsible to provide reasonable values and, if an application receives event dates, has to make consistency checks by their own.
IfcEventTime furthermore provides a generic mechanism to differentiate between user given time values and time values derived from user given time values and other constraints such as work calendars and assigned resources (derived from the process graph). The data origin flag is provided as a single attribute applying to all date time related attributes of IfcEventTime.
HISTORY New entity in IFC4.
|1||Name||OPTIONAL IfcLabel||Optional name for the time definition.|
|2||DataOrigin||OPTIONAL IfcDataOriginEnum||Specifies the origin of the scheduling time entity. It currently|
differentiates between predicted, simulated, measured, and user defined values.
|3||UserDefinedDataOrigin||OPTIONAL IfcLabel||Value of the data origin if DataOrigin attribute is USERDEFINED.|
|4||ActualDate||OPTIONAL IfcDateTime||The date on which an event actually occurs. It is a measured value.|
|5||EarlyDate||OPTIONAL IfcDateTime||The earliest date on which an event can occur. It is a calculated value.|
|6||LateDate||OPTIONAL IfcDateTime||The latest date on which an event can occur. It is a calculated value.|
|7||ScheduleDate||OPTIONAL IfcDateTime||The date on which an event is scheduled to occur. |
The value might be measured or somehow calculated, which is defined by
ENTITY IfcEventTime SUBTYPE OF (IfcSchedulingTime); ActualDate : OPTIONAL IfcDateTime; EarlyDate : OPTIONAL IfcDateTime; LateDate : OPTIONAL IfcDateTime; ScheduleDate : OPTIONAL IfcDateTime; END_ENTITY;