Layer Combinations, Best Practices

[Anonymous]

When working with several architects and engineers, are there some best practices for how to name and arrange layer combinations?

..or somehow some guidelines about how it should look like when exporting to IFC?

[Erwin Edel]

We use abreviations to sort them by topic / type / category / design stage and such. Structural, Facade, Section, Electrical, Footings, Ceiling plans, etc etc and then some for different scales like 1:5, 1:20, 1:50, 1:100 etc

We do have some in IFC category for the different third parties (architectural model, structural model, MEP model, importing)

We tend to name clones (views) following the same method: abreviation as ID and the description as Name. So most clones will have dedicated layer combinations

We sort 'custom' working layer combinations to top or bottom with adding things to abreviation to make sure that happens.

99% is already setup in template. People know what element goes on what layer, so very little need to customise what is there in terms of layer combinations.

Couple of things that might be worth noting:
We have just over 100 layers in our projects ussually, so easy to manage
Around 50 layer combinations covering pretty much all that is needed

We use the same convention for our model view options, graphic overrides and rulesets, so it is clear what belongs where when saving views. Just match the same abreviation code in layer combo, mvo, go.