Anuncios
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!
Comentario
Advocate
Advocate

Rudi,

 

Thanks for your reply! It is really interesting to read some of the problems you have. I am from a clearly much smaller company of 35 people and most of the issues you talk about are yet to crop up - however I can definitely see some users in my company doing as you suggested. 

 

I think I have made the statement that Autodesk shouldn't work on this, and that's not how I feel. I want them to work on it, but I want them to work on other things more as they are bigger issues for myself. 

 

You're not wrong: until we take humans out of the equation, humans will screw it up. That being said, a lot of the issues you have brought up are people making really bad choices/not being at all skilled at using Revit and that argument could be used for not using Revit at all... 

 

Some that are more of a problem with the workaround I've suggested are as follows:

  • I don't think you can argue that training isn't part of the process - everyone has to have some training in order to use Revit, it's not a simple program to use. I don't find that to be a particularly valid argument.
  • Levels being deleted - agreed this can be a problem, although surely there is one level that will never be deleted (ground, for instance) and you can maintain that throughout a project. Also you mention people copy monitoring levels when they shouldn't - that's an error that needs to be ironed out in your training. 
  • Worksets being closed - we do not work on projects where worksets need to be closed, although i would argue that a workset for schematics could mitigate this entirely as someone who was plotting surely ought to make sure they had the correct worksets open when exporting any information and if there was one called 'Schematics' and they were issuing schematics, they have done a serious mistake haven't they?
  • We actually have our own line-based detail items which we use for pipes, ducts etc - we don't use detail lines for anything, so we don't have the problem of converting detail lines to model lines - as a result, i didn't even know that you could. Also as an aside, using line based detail items for pipes and ducts allows us to put to actually put info into the detail items and use tags to pull that info off, rather than using text. Not sure if you've thought of this but might be a top tip for you.
  • Not sure where CAD files come into the workflow/workaround we are talking about - guess you mean that people are doing the schematics in AutoCAD then bringing them into the model for issuing - but your text won't scale and this breaks your own suggestion as far as i can tell. 
  • As above, i agree level deletion is something to worry about but surely there is 1 level per project which shouldn't ever get changed and the schematics could be modelled on that? I agree this is something to think about that you would not have to think about with Drafting views.
  • Deleting model elements shouldn't be an issue as long as you have a View template set up with no model elements visible. Again another thing you wouldn't need to do in Drafting views, but only needs doing a single time which would take all of 10 minutes and then added to the template and you're sweet!

My final response is as follows: How do you know it is a quick win to add this functionality to Drafting views? Unless you have programmed the plans and drafting views portion of Revit yourself, surely you can't possibly know how easy or difficult, quick or slow, adding scope boxes to drafting views can be. You shouldn't make such accusations without intimate knowledge of the process involved. It's definitely a win but it might not be quick or easy.

 

Thanks,


Ben