Revit Warnings - some insight?

[rbcameron1]

Can anyone shed some light as to why Revit warnings were created? I understand how to resolve them and how to avoid them, but is there any insight someone can post as to their importance? I feel like "duplicate marks" really isn't a big deal since they are easy to resolve and don't really cost the model all that much. Other issues like stairs not meeting floor heights are more understandable, but in reality you would review stairs on the project before it went out the door. I don't really need Revit to tell me I'm missing a riser...
How much file size would 100, 1,000 or 5,000 warnings add to a Revit model? What is an acceptable number of warnings (besides 0) are people ok with?

[cdatechguy]

It's a program full of data...having the same identification number for two different elements slows it down....or

You can have 5000+ warnings and it won't affect the file size...what it does affect is model performance. I have gotten a model with 5000+ warnings and got it down to 100....big improvement in performance. But a lot of them are stupid, no way of actually fixing them, errors that I tend to ignore...like having a window touch a wall...really?

[damon.sidel]

They may not always be helpful, but I can think of a lot of great warnings I've gotten that are helpful. When a multi-level wall is moved and conflicts with an opening on a different level, that's helpful. Knowing the stair doesn't work is helpful. Yes, you should review that, but especially in early phases when you aren't drawing stair sections and the stair isn't prominent in 3D, it's just convenient.

[MikeJarosz]

Maybe Revit should have an "expert" setting that turns off warnings for experts such as Mr Cameron:)

[rbcameron1]

Could there be a way to shut them off? haha! Especially when the "one of your curtain panels is malformed-This issue is likely ignorable...etc..." warning pops up.
Just looking to put together some information here at my firm on the subject. I know warnings are important but sometimes it feels like busy work trying to resolve all the issues. Or am I mistaken and everyone loves having 52 new warnings to go through when they get in every monday morning?

[cliff collins]

I think the fact that they are called "Warnings" is pretty self-explanatory. A warning just means "alert--there might be a problem, please take a look".

The software is just reporting concerns--and it even tells you if they are minor/can be ignored, or if they are more severe.

If you ignore them, the project will continue to suffer performance problems or perhaps even become corrupt. If you learn to quickly sift through the warnings and address the more critical ones, you will have a more efficient project. It is a "learned behavior"--after years of looking at Warnings you will become better at deciphering and addressing them.

It is also important to expose the Warnings to your user team, so they are aware of them, how they are generated--i.e. how "sloppy modeling" affects the project, etc.

Having duplicate elements may not seem like a big deal--but if the model is to be used downstream by a GC/CM/sub for estimating, it can lead to major inaccuracies and affect the $/budget!

I do agree that the documentation could be a bit better in explaning Warnings, and how to filter through and reconcile them. Jeff? any thoughts?

[antman]

52 new warnings per week? Seems like a lot. My current project has about 140. I don't have time to go through them today, but next week I will. I can probably get that number under 20. Now that I've gone through this list, however, it occurs to me that these warnings are not so much something that will kill the project, but opportunities to spot areas that require some additional training and mentoring.

[CADastrophe]

You should see this on the MEP side - just opened a Project I haven't worked on in a while and it has an even 10,000 Warnings. Only 1,421 of them are "Elements have duplicate 'Mark' values". This should be fun to clean up!

[rbcameron1]

52 new warnings per week? Seems like a lot.<--> ...but opportunities to spot areas that require some additional training and mentoring.

That's what I'm hoping to get at, is pinpointing some common errors so they can be avoided. 52 is high and that's not every week, just one week a year, maybe two. It's always something though. Thanks for the heads up everyone.

[jsteinhauer]

I tell my coworkers to keep warnings under 500. They're pretty easy to take care of if you keep on top of them from the beginning. I have 78 warnings in my current project, all of which are caused by a connector family not having loss data assigned to it. I should delete the connectors in my family, then I'd have 0 warnings. When well Revit recognize connectors between linked files? It would save so many headaches for coordination.

Cheers,
Jeff S.