Pipes/ Ducts — Notes
Provenance
- Source: CORENET X Code of Practice v3.1, Section 4 (BIM Data Representation — IFC+SG), pages 74–76.
- Source link: CORENET X — IFC-SG Glossary of Identified Components ↗
- Discipline: MEP · Authorities: —
- 6 IFC binding(s), 30 parameter(s), 1 declarative-only binding(s).
IFC binding breakdown
IfcPipeSegment— subtypes: RIGIDSEGMENT, FLEXIBLESEGMENT — 12 param(s), table format6col.IfcDuctSegment— 5 param(s), table format6col.IfcDuctFitting— 5 param(s), table format6col.IfcPipeFitting— subtypes: BEND, DRAINCHANNELBEND, ENTRY, EXIT, FLANGEADAPTOR, FLEXIBLECOUPLING, JUNCTION, OBSTRUCTION, PIPESILENCER, SHORTPIECE — 6 param(s), table format6col.IfcAirTerminal— subtypes: GRILLE, LOUVRE — 2 param(s), table format6col.IfcPipeSegment— subtypes: SCUPPERDRAIN, SPOOL, FLARESTACK, RAINWATEROUTLET — 0 param(s), table format6col. [no IFC+SG properties required]
Other input-limited parameters
These accept values from a defined list in the COP source table (not part of the global structural enums); see examples in parameters.json:
- PreInsulated, Perforated, TradeEffluent, DemountableStructureAbovePipe