Defined in File Ifc4x1.h
public Ifc4x1::IfcConstructionEquipmentResourceType(Class Ifc4x1::IfcConstructionEquipmentResourceType)
public Ifc4x1::IfcConstructionMaterialResourceType(Class Ifc4x1::IfcConstructionMaterialResourceType)
public Ifc4x1::IfcConstructionProductResourceType(Class Ifc4x1::IfcConstructionProductResourceType)
public Ifc4x1::IfcCrewResourceType(Class Ifc4x1::IfcCrewResourceType)
public Ifc4x1::IfcLaborResourceType(Class Ifc4x1::IfcLaborResourceType)
public Ifc4x1::IfcSubContractResourceType(Class Ifc4x1::IfcSubContractResourceType)
IfcConstructionResourceType: public Ifc4x1::IfcTypeResource¶
IfcConstructionResourceType is an abstract generalization of the different resource types used in construction projects, mainly labor, material, equipment and product resource types, plus subcontracted resource types and aggregations such as a crew resource type.
A resource type represents a model of “use of something” and does not necessarily correspond to a specific type of object such as a person or vehicle, but represents possible usages of such objects such as general labor or an equipment fleet. A resource type can either represent usage in general (consumption attributes defined but no task type assignment) or a task-specific resource type (production attributes defined and having an IfcTask assignment).
A construction resource type captures common productivities and cost rates for applying resources to particular task types.
HISTORY: New entity in IFC2x4.
Composition use definition Resource types may be decomposed into nested resource types indicating productivities when applying the resource to specific task types using the IfcRelNests relationship where IfcRelNests.RelatingObject refers to the general resource type and IfcRelNests.RelatedObjects refers to one or more task-specific productivities. For example, an IfcLaborResourceType may be defined for “Carpenter” which may have a nested IfcLaborResourceType for “Carpenter - Wall Framing” and another nested IfcLaborResourceType for “Carpenter - Drywall”, each of which may have productivities based according to specific task types (IfcTaskType).
Assignment use definition Resource types may be assigned to process types (IfcTypeProcess subtypes) using the IfcRelAssignsToProcess relationship as shown in Figure 193. Such relationship indicates that the resource type applies to the process type for the use indicated (e.g. IfcTaskType.PredefinedType). Such relationship enables a scenario of placing an IfcProduct of a particular IfcTypeProduct, querying for a set of IfcTypeProcess process types for constructing such product (e.g. IfcTaskTypeEnum.CONSTRUCTION), querying each IfcTypeProcess for a set of IfcTypeResource resource types for carrying out the process, and finally choosing an IfcTypeProcess and IfcTypeResource combination resulting in the shortest time for instantiated IfcTask occurrence(s) and/or lowest-cost for instantiated IfcConstructionResource occurrence(s).
Figure 193 — Construction resource type assignment
Subclassed by Ifc4x1::IfcConstructionEquipmentResourceType, Ifc4x1::IfcConstructionMaterialResourceType, Ifc4x1::IfcConstructionProductResourceType, Ifc4x1::IfcCrewResourceType, Ifc4x1::IfcLaborResourceType, Ifc4x1::IfcSubContractResourceType
Whether the optional attribute BaseCosts is defined for this IfcConstructionResourceType.
Whether the optional attribute BaseQuantity is defined for this IfcConstructionResourceType.
IfcConstructionResourceType(std::string v1_GlobalId, ::Ifc4x1::IfcOwnerHistory *v2_OwnerHistory, boost::optional<std::string> v3_Name, boost::optional<std::string> v4_Description, boost::optional<std::string> v5_ApplicableOccurrence, boost::optional<IfcTemplatedEntityList<::Ifc4x1::IfcPropertySetDefinition>::ptr> v6_HasPropertySets, boost::optional<std::string> v7_Identification, boost::optional<std::string> v8_LongDescription, boost::optional<std::string> v9_ResourceType, boost::optional<IfcTemplatedEntityList<::Ifc4x1::IfcAppliedValue>::ptr> v10_BaseCosts, ::Ifc4x1::IfcPhysicalQuantity *v11_BaseQuantity)¶