@lmolina6V6K7 wrote:
I guess this is a very subjective subject.
Not at all. Your logic is either flawed or your use of the term "template" is incorrect in this forum.
A template does not drive the standards. The standards drive the template. It sounds like you are talking about a standards check.
A project template is merely a starting point. If the wrong template was used, it should be apparent with a standards check. If standards require that the standards included in the template are not to be changed, then the starting project template should be defined in the standards. In this case, the correct starting template is known and if there is any doubt that the wrong one was used, then the correct standards should be applied in whatever way is appropriate to get everything correct. There is no need to know which one was used, just which one should be applied.
This thread is mostly about models from consultants. If you don't have their template named Charlie, how is knowing that they used Charlie to start the project going to help you unless you have said template? What if massive standards changes were made during the project because the project required it? I honestly don't see how knowing which template the project was started with is going to help. You need to know what the correct standards are. The template might help with that but it isn't where you should be looking. You need to look at the standards used to create the template.
Further thought leads me to think that you may be referring to a project prototype which could lead to confusion when using the term template. A prototype defines more than just what is included in a typical project template. I've come across these when doing chain stores where every one is almost the same as all the others with minor modifications to suit the particular project site.
@lmolina6V6K7 wrote:
For us, as an organization, is more valuable to know right away if a project is not using the approved standards.
Knowing the template isn't going to help with that. Just because a project was started with a template doesn't mean it is still using the standards within it.
@lmolina6V6K7 wrote:
At 30% of the project, even some cases at 60% is worth to go back and start from scratch rather than start scrutinizing the project template, transferring and updating all non-standard elements.
Really? Starting over at 60% is an option in your world? Doesn't that kill the profit margin? Standards checking should be done throughout the project on a regular basis to avoid this type of thing. If you do need to start the project over, your standards will tell you which template should be used not the template that was used to start errant project but you shouldn't need to start the project over, just apply the correct standards in a way that doesn't destroy the model.
I really don't understand the logic that you are trying to apply here. It's not the template that matters, it's the standards. I think you're barking up the wrong tree.
Rob
Drafting is a breeze and Revit doesn't always work the way you think it should.