buildingSMART / buildingSMART/IFC4.x-development

Allow Pset_ConstructionOccurence to also be used on IfcGroup for Systems

Open
#789 0 comments 0 reactions 0 assignees View on GitHub
after-NWI
Dominant language
Python
Stars
234
Forks
123
Avg merge
15h 4m
Merged PRs (30d)
5

Description

In Asset Management Registers there is a need to uniquely identify not just the actual individual, but also it’s sub- and main system. By allowing the use of Pset_ConstructionOccurence also on the actual system it belongs to it would give the asset manager the possibility of having one single Pset for identifying it's assets.

Example:
An IfcLightFixture _AB+2111K=631BA090_
Fitted on IfcMember.POST _AB+2111K=631PS090_
add a few IfcPipeSegment.FLEXIBLESEGMENT and you have a circuit (or a group) _AB+21184=631WC001-7_
then add to this the Mains cabinet IfcElectricDistributionBoard.SWITCHBOARD _AB+21184=631WC001

They all belong to an IfcDistributionSystem.LIGHTING **_V=C.VS=QGA.EA001_**

![Bild1](https://github.com/buildingSMART/IFC4.3.x-development/assets/124705278/d2ad7316-c7db-41a3-8596-b945fa6c2f1a)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the IFC schema definitions and usage rules for Pset_ConstructionOccurence, IfcGroup, and IfcDistributionSystem. Compare the asset and system examples in the issue, then determine the schema changes and validation needed so the property set can identify the relevant group and system consistently.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.