Quantities in Navisworks NOT accurate - major fail

Quantities in Navisworks NOT accurate - major fail

Anonymous
Not applicable
1,154 Views
3 Replies
Message 1 of 4

Quantities in Navisworks NOT accurate - major fail

Anonymous
Not applicable

Hi all,

 

I have a serious issue with the quantities that Navisworks is giving me in the Quantification tool.

This issue has been around for ages - and to my astonishment - still has not been sorted out in Navisworks (a >10K software tool).

This makes the i in BiM pretty useless from my personal point of view.

And this is a serious issue Autodesk, that can have major influences on projects making use of the quantities from Navisworks...

Am I to blunt in saying so, or just missing some basic knowledge? 

What am I doing wrong? NWC export setup?

 

Cheers,

Cyrille

 

 

0 Likes
1,155 Views
3 Replies
Replies (3)
Message 2 of 4

dgorsman
Consultant
Consultant

Could you describe the actual problem please?  FYI, we've recently had a swarm of PDF attachments in the forums being used to get around the spam filters so in doing so you may not get the level of response you are looking for.

----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.


0 Likes
Message 3 of 4

Anonymous
Not applicable

Thanks for the headsup dgorsman,

 

The issue I am referring to is that the Surface area of objects withing Navisworks are NOT correct. And therefore are a great risk.

 

Example:

I have modelled a rectangular ceiling object in Revit.

Export to .NWC and.IFC

Import the .NWC or .IFC in Navisworks, then I measure ceiling object to have the following dimensions: W: 2025mm *  L: 9011mm => this should give me an Area of: 18.247m2 

When selecting the ceiling object, its properties show me: 1695133mm2 = 1.695m2

When using the Quatification Workbook the Area is 1.695m2

 

When measuring the Area in Revit, Tekla BIMsigh or Solibri Model Checker the surface area is 18.247m2

 

Cheers,

Cyrille

0 Likes
Message 4 of 4

Anonymous
Not applicable

So I just found out that the .NWC export was the problem. Somehow the export was error prone. If I replicate the issue with a new object modelled in Revit, do the .NWC export, then its all fine.

 

0 Likes