[Otázka] Roof Covering (Dachhaut) : Several Issues


Hi all,

-----------------

Previous Notes:

The new tool "Roof covering" (Dachhaut), it's a really very powerful tool. Conceptually, the usability is equal like wall tool, we love it. But internally, it's very different how wall tool works.

- In walls, every wall has only one parent (total wall), and several childs (wall layers) -> How wall works internally, it's perfect to manage data inside Allplan, reports, IFC, and so on.

- In a roof covering, every child (roof covering layer) has a parent. There isn't only one parent for all layers: then, if a roof covering have 3 layers, there are also 3 parents -> It's a madness: adds a lot of complexity in order to manage data inside Allplan, reports, IFC....

-------------------

Detected Issues:

Issue 1 - Some modifications in "Roof Covering" dialog box, are not saved. For example, material. This issue is showed in video "Issue_1_Modification"

Issue 2 - In report or export to excel using "Export Attributes" or "Export Quantities Data", shows incorrect allplan internal IDs of the "roof coverings", and this affects parents and childs. This issue is showed in video "Issue_2_Report_ID"

I also upload a zip file that contents: a NDW and RDLC files.

Best regards.
Xavier Coll
EiPM

Xavier Coll • Architect, Project Manager I+D, BIM Manager, BIM Auditor
EiPM • http://www.eipm.es/en/

Přílohy (3)

Type: video/mp4
Staženo 140
Size: 1,24 MiB
Type: video/mp4
Staženo 134
Size: 2,02 MiB
Type: application/zip
Staženo 128
Size: 14,68 KiB
11 - 13 (13)

Dear Xavier,

thank you for your feedback.
Once there are few points you described, needs to be solved individually.
Problems with importing attributes without enabled option with dialog box comparing data needs to be checked. It looks like in that case Material attributes are messed up somehow, which causes the duplicate IDs of parrent/child and problems with Material changes afterwards.
The parrent / child structure of Roof covering {in case of more layers} looks for me obsolete, not knowing the context of such implementation in the far past. We would like to change it in future versions of Allplan to have consistent behavior parent/child similar to Wall/Wall layers.

S pozdravom | Best regards | Mit freundlichen Grüßen

Martin Mikus
Product Manager Allplan Architecture

Citoval Nemo
As explained, I use Allplan 2019!
Maybe there is something changed to 2020...

Good afternoon Nemo,

I just install 2019-1-12, and also It have the same issue like 2020-1-2, of repeated ID in the exported list...

I upload a video, showing the issue.

Best regards,
Xavier Coll
EiPM

Xavier Coll • Architect, Project Manager I+D, BIM Manager, BIM Auditor
EiPM • http://www.eipm.es/en/

Přílohy (2)

Type: video/mp4
Staženo 70
Size: 2,12 MiB
img
2019_Roof covering_repeated IDs.png
Type: image/png
Staženo 2
Size: 187,54 KiB

Citoval MartinMikus
Dear Xavier,
thank you for your feedback.
Once there are few points you described, needs to be solved individually.
Problems with importing attributes without enabled option with dialog box comparing data needs to be checked. It looks like in that case Material attributes are messed up somehow, which causes the duplicate IDs of parrent/child and problems with Material changes afterwards. The parrent / child structure of Roof covering {in case of more layers} looks for me obsolete, not knowing the context of such implementation in the far past. We would like to change it in future versions of Allplan to have consistent behavior parent/child similar to Wall/Wall layers.

Thanks Martin for your answer!

The issues we explained about Allplan 2020, also exist in previous versions.....

Well, we think that Allplan needs some improvements and rationalize several basic tools, in order to manage project data more efficiently, in a scope to data management of massive processes. For example, the same tool "Roof covering" doesn't have Thickness attribute like Wall or slab have... (see image attached): this misalignment of attributes and data, it don't helps so much to do queries or management of data in massive and global processes, when every modeling tool have the data stored in different ways.

An IFC Exporter, for this to be really powerful, must:
- Remapping attributes correctly (currently doesn't do well)
- Create calculated Attributes in IFC. Okay, now inside Allplan, it's possible to add new calculated attributes and compute them with Export / import processes using XAC or XSLX: but Allplan does NOT really have a good global data manager, and by now, It's still really complex, hard and heavy.

These two commented points would allow:
- Allplan Could have the best IFC Export in the market: this will benefit for projects carried out with Allplan, benefit for BIM plus, benefit for clients who receive models. And at the level of marketing, this could be very beneficial, and a punch to competitors.
- To focus to obtain an IFC with data correctly structured and aligned between the different construction systems of a project, could help the development team to free them from the burden of reprogramming Allplan code to align and rationalize the program, since it would be at IFC where they would be aligned. the data.

We will waiting for allplan improvements about those issues (and from others..)

thanks a lot!
Xavier Coll
EiPM

Xavier Coll • Architect, Project Manager I+D, BIM Manager, BIM Auditor
EiPM • http://www.eipm.es/en/

Přílohy (1)

img
Roof Covering_Thickness.png
Type: image/png
Staženo 12
Size: 94,43 KiB
11 - 13 (13)

https://campus.allplan.com/ používá cookies  -  Více informací

Souhlasím