archive-org.com » ORG » B » BUILDINGSMART-TECH.ORG

Total: 393

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • #CV-2x3-166 — Welcome to buildingSMART-Tech.org
    2x3 166 based on IFC2x3 effects Coordination view version 2 0 date September 2010 initiator official buildingSMART certification 2 0 program summary agreement to not use deprecated IfcElectricHeaterType for electrical space heaters Description The use of the deprecated IfcElectricHeaterType is not allowed as it will not be supported in the next IFC4 release electric space heaters shall be represented by IfcFlowTerminal for individual occurrences and IfcSpaceHeaterType for common type information Addition 2013 04 10 The following applies to all space heater independent of source of energy supply the individual occurrence is of type IfcFlowTerminal the common type information is of type IfcSpaceHeaterType NOTE this supersedes the documentation in IFC2x3 where electric space heaters occurrences are defined as IfcFlowTerminal and non electrical as IfcEnergyConversionDevice and it is in line with the improved definition in IFC4 Previous CV 2x3 165 Next CV 2x3 167 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 166 IFC Impl Guide IFC Header Guide IFC4 impl guidance Implementer s community accompanying documents frequently asked questions Implementations Search Advanced Search IFC Dev Blog IFC Dev Blog More Registration This site contains content which is only available to registered users To get

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-166 (2016-02-11)
    Open archived version from archive


  • #CV-2x3-167 — Welcome to buildingSMART-Tech.org
    agreement to assign style to all body shape representations Description For all instance of a subtype of IfcProduct the following has to be fulfilled If the instance has a Body shape representation then there shall be a style information minimum a surface color optional additional surface rendering colors and line color attached The style information may be assigned in the order of overriding in case of multiple assignments from lowest to highest priority to the material assigned to the subtype of IfcTypeProduct being the type of the instance of IfcProduct accessible via SELF IfcObject IsDefinedBy IfcTypeObject HasAssociation IfcRelAssociatesMaterial to the material assigned to the instance of IfcProduct as IfcMaterialDefinitionRepresentation accessible via SELF IfcObjectDefinition HasAssociation IfcRelAssociatesMaterial to the main representation item in set IfcShapeRepresentation Items using IfcStyledItem to the subsequent geometric representation item referenced by the main geometric representation item e g the mapped representations referenced by the IfcMappedItem or the IfcExtrudedAreaSolid referenced by IfcBooleanClippingResult Previous CV 2x3 166 Next CV 2x3 168 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 167 IFC Impl Guide IFC Header Guide IFC4 impl guidance Implementer s community accompanying documents frequently asked questions Implementations Search Advanced Search IFC

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-167 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-168 — Welcome to buildingSMART-Tech.org
    view version 2 0 date September 2011 initiator official buildingSMART certification 2 0 program summary agreement to use standard shape representation type names Axis FootPrint also for IfcStairFlight and IfcRampFlight Description In order to rationalize the use of representation types IfcShapeRepresentation RepresentationType to have it consistently as Axis for a line based representation and FootPrint for ground floor the agreement of correct use of representation types for IfcStairFlight and IfcRampFlight is altered The current definition from the IFC2x3 specification for IfcShapeRepresentation for IfcStairFlight and IfcRampFlight is as following WalkingLine A two dimensional open curve IfcBoundedCurve defining the walking line for the stair flight Boundary A two dimensional closed curve IfcBoundedCurve defining the boundary of the stair flight The new Implementer Agreement CV 2x3 168 introduces the renaming of the representation type names into IfcShapeRepresentation RepresentationIdentifier Axis IfcShapeRepresentation RepresentationType Curve2D GeometricCurveSet IfcShapeRepresentation RepresentationIdentifier FootPrint IfcShapeRepresentation RepresentationType GeometricCurveSet Previous CV 2x3 167 Next CV 2x3 169 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 168 IFC Impl Guide IFC Header Guide IFC4 impl guidance Implementer s community accompanying documents frequently asked questions Implementations Search Advanced Search IFC Dev Blog IFC Dev Blog More Registration This

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-168 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-169 — Welcome to buildingSMART-Tech.org
    restrict which independent elements can be contained in a building spatial structure Description The following entity instances shall not be used as an independent element that is assigned to the spatial structure IfcBuildingElementPart it shall only be used as a part of an aggregate IfcRampFlight it shall only be used as a part of an aggregate being of type IfcRamp IfcStairFlight it shall only be used as a part of an aggregate being of type IfcStair IfcDistributionPort it shall only be used as a port assigned to a distribution element The following definitions apply assigned to spatial structure the element has an inverse relation ContainedInStructure to a subtype of IfcSpatialStructureElement via IfcRelContainedInSpatialStructure part of an aggregate the element has an inverse relation Decomposes to another element via IfcRelAggregates used as a port the IfcPort or subtype has an inverse relationship ContainedIn to an element via IfcRelConnectsPortToElement In addition no subtype of IfcFeatureElement such as IfcOpeningElement shall be assigned to a spatial structure Previous CV 2x3 168 Next CV 2x3 170 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 169 IFC Impl Guide IFC Header Guide IFC4 impl guidance Implementer s community accompanying documents

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-169 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-170 — Welcome to buildingSMART-Tech.org
    0 Therefore the following agreement is imposed The software application supporting export of CSG shape representations shall have an export configuration setting to enable the export of CSG geometry as an option for the IFC2x3 Coordination View V2 0 However the default export setting for the IFC2x3 Coordination View V2 0 shall disable CSG to avoid incompatibility issues with current IFC import interfaces The default setting shall force the export as Brep shape representation for those elements The export setting shall only affect the elements otherwise being exported as CSG and not all element shape representations i e it is not a replacement of the IFC2x3 simple presentation view having ALL elements exported as Brep s also as CSG is a solid the Brep representation is required being a solid and not a surface model representation The export setting user interface shall have a proper explanation that the CSG setting may cause interoperability issues with older IFC implementations e g the previous IFC2x3 Coordination View V1 0 NOTE Within the IFC2x3 Coordination View V2 0 certification process a second test file not containing CSG representation is required for each export test case having a test file with CSG shape representations

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-170 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-171 — Welcome to buildingSMART-Tech.org
    representation identifier shall be used twice within the product representation of an element number CV 2x3 171 based on IFC2x3 effects IFC2x3 coordination view 2 0 date 24 Oct 2011 initiator ISG meeting in Budapest summary no shape representation identifier shall be used twice within the product representation of an element Description Any product representation of an element may have multiple shape representations However there shall be no two or more IfcShapeRepresentations having the same RepresentationIdentifier within one IfcProductDefinitionShape Example it is not allowed to export two Body shape representations for an element The following snipped is incorrect and will lead to a validation error 200 IFCSHAPEREPRESENTATION 100 Body CSG 210 error 300 IFCSHAPEREPRESENTATION 110 Body Brep 310 error 400 IFCPRODUCTDEFINITIONSHAPE 300 200 error Previous CV 2x3 170 Next CV 2x3 172 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 171 IFC Impl Guide IFC Header Guide IFC4 impl guidance Implementer s community accompanying documents frequently asked questions Implementations Search Advanced Search IFC Dev Blog IFC Dev Blog More Registration This site contains content which is only available to registered users To get access to the content you must be a registered user

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-171 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-172 — Welcome to buildingSMART-Tech.org
    of regular patterns number CV 2x3 172 based on IFC2x3 effects IFC2x3 coordination view 2 0 date 24 Oct 2011 initiator ISG meeting in Budapest summary enable multiple mapped items as a shape representation of regular patterns Description Elements having pattern like arrangement of components such as a bolt nail group a group of reinforcement bars etc are best defined in terms of their geometry as multiple mapped items referring to the same representation map This implementer agreement makes a preference to export such multiple mapped items and requires the correct import of multiple mapped items In addition it provides a guideline to implement it The following figure shows how multiple mapped items shall be implemented as the Body shape representation of such elements as e g an IfcFastener Previous CV 2x3 171 Next CV 2x3 173 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 172 IFC Impl Guide IFC Header Guide IFC4 impl guidance Implementer s community accompanying documents frequently asked questions Implementations Search Advanced Search IFC Dev Blog IFC Dev Blog More Registration This site contains content which is only available to registered users To get access to the content you

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-172 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-173 — Welcome to buildingSMART-Tech.org
    than one part number CV 2x3 173 based on IFC2x3 effects IFC2x3 coordination view 2 0 date 24 Oct 2011 initiator ISG meeting in Budapest summary aggregates shall have more than one part Description All elements and element types that are exported as an aggregate shall have more than one component The IfcRelAggregates relationship pointing to the subtype of IfcElement being the container element shall therefore have two or more RelatedObjects NOTE In exceptional cases an aggregate may have only one component therefore it is reported as a warning within the validation process On import software applications shall accept aggregates with one or more components An aggregate is a subtype of IfcElement or IfcElementType having the INV relationship IsDecomposedBy established and pointing to an IfcRelAggregates relationship Previous CV 2x3 172 Next CV 2x3 174 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 173 IFC Impl Guide IFC Header Guide IFC4 impl guidance Implementer s community accompanying documents frequently asked questions Implementations Search Advanced Search IFC Dev Blog IFC Dev Blog More Registration This site contains content which is only available to registered users To get access to the content you must be a

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-173 (2016-02-11)
    Open archived version from archive



  •