Schedule room finishes from bounding *surfaces*

[Anonymous]

We'd like to automate our interior finishes scheduling but can't find a (consistent) way to pull floor/wall/ceiling attributes from the building model. Could be surface material, could be surface fill (related to material I know but perhaps this can be requested in a way the material cannot...).

The simplest way might be to request materials from the source zones, where each surface material is inherited from the bounding construction (already an option under the 'model' tab though it only works at the walls and doesn't currently alter the bottom/top surfaces to match adjacent floor/ceiling elements). This call doesn't currently exist.

Alternatively the zone could request some attribute (material/cut fill/surface fill) of the wall surface adjacent/composite skin closest. Currently these calls seem to deliver multiple responses ie all cut fills across the depth of a composite wall not just the relevant (closest) skin.

Current workaround is to create text fields in the zone properties which are used to populate the schedule. But automatically pulling a name or code from the actual bounding elements would be the BIM approach surely. Seems so simple but I cannot make it happen. Grr.

[Anonymous]

So is there a way to do it nowadays?

[Laszlo Nagy]

There are now Surface Schedules in ARCHICAD 19:

https://www.youtube.com/watch?v=H2TAgQBRPLU

https://www.youtube.com/watch?v=vpU3euwD-kU

[Anonymous]

So it seems.

Now, what would be really useful would be that if you were able to get listing of the surfaces bounding the zone; What's usually required with renovation projects is surface listing of each room.
For that it would be essential to be able to run listing of each's room's (ie zone's bounding) walls, floors and ceilings. Like:

zone001
floor: laminate, gray – N m2
walls: painted, white – N m2, painted, green N m2
Ceiling: Paneling, gray – N m2

Ay possibility?

[Laszlo Nagy]

Yes, that would be a good next step.
At the moment it is not possible to get the surface of an element (e.g. a Wall) that is the boundary surface of a given Zone.
We would probably need two new Zone listing parameters:
1. Boundary Surface Area
2. Element of Boundary Surface

1. would list the total surface areas of each different Surfaces found on the boundaries of a given Zone.
2. would list the element a given surface belongs to.

So if only 1. would be listed for a zone you would get something like this (individual areas of the various surfaces on the boundary elements of a given Zone):

zone001
laminate, gray – N m2
painted, white – N m2
painted, green N m2
paneling, gray – N m2

However, if you listed both 1. and 2. you would get this (surfaces listed by element):

zone001
floor: laminate, gray – N m2
wall1: painted, white – N m2, painted, green N m2
wall2: painted, white – N m2, painted, green N m2
wall3: painted, white – N m2, painted, green N m2
wall4: painted, white – N m2, painted, green N m2
Ceiling: Paneling, gray – N m2

Thinking now a bit further, there could be more parameters such as

3. Element Type of Boundary Surface
4. Element Classification of Boundary Surface

If 1. and 3. were listed you would get the result you would like to achieve:

zone001
floor: laminate, gray – N m2
wall: painted, white – N m2, painted, green N m2
Ceiling: Paneling, gray – N m2

4. would be useful in cases where a certain element type is used to model another element type (e.g. a Roof is used to model a Slab). If the Roof was classified as a Slab, then 1. and 4. listed it would give the result:

zone001
slab: laminate, gray – N m2
wall: painted, white – N m2, painted, green N m2
Ceiling: Paneling, gray – N m2


So there are quite a few possibilities here and the Surface schedule could be further developed to be even smarter.

[furtonb]

Is there any news on this?

I've tried to convert the Zones to Morphs and schedule the surfaces from them, but the surface overrides from the Zone bounding elements (Walls in my case) are getting reverted to the surface defined in the Zone settings.

Pity, could've been an easy workaround.