I wrote the following at AUGI the other day:
First a silly message from the Management
More seriously, do focus on warnings that:
A team needs to know they exist and why they are there. The quantity of them varies wildly as a design evolves. If the team is aware and tracking them then they don't turn into thousands of errors that negatively affect the project.
First a silly message from the Management
- Procedure Item: Review Warnings
- Steps: Review and FIX them!!
- Thank you, the mgmt!
More seriously, do focus on warnings that:
- Affect calculations, rooms/areas & wall/boundary errors
- Duplication (multiple elements in the same place)
- Affect documentation - Type Marks/Marks/tagging accuracy
A team needs to know they exist and why they are there. The quantity of them varies wildly as a design evolves. If the team is aware and tracking them then they don't turn into thousands of errors that negatively affect the project.
No comments:
Post a Comment