Copy/Monitor - But don't monitor
Well for concrete structure that's a different sort of issue than steel structure since joining geometry isn't nearly the factor for steel as it might be for concrete.
Automatic is a rabbit hole of undetermined depth and complexity. The software solutions we get never cover every iteration we can throw at them. If there is a consistent repeated process that can be defined well and used by many the chances of it getting included improves...
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
The documentation for all things never does a perfect job. The description is very general, describing the intent but without delving into each categories behavior and purpose. Executive summaries, always attempt to distill the broad purpose or data provided in a report. Help/documentation files are no different.
The copy/monitor function does what you expect for levels and grids. It does not do that for columns because they designed it that way...because user input and their own experience said they should do it this way. Your expectations and goals are different...no surprise really. That's true for nearly everything in life. The developers know in advance that every solution they provide will run into someone that doesn't agree with it's approach. They try hard to meet the needs as many users as they can.
In this case, you have to go the Revit Ideas path to get your preferences in front of them to make them reconsider their decision. In the short term consider creating/buying a 3rd party application to compare columns in the same location and different types.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
When Copy/Monitor and Coordination Review was introduced, at the arrival of Revit Structure 1 (in 2005), the only categories involved were Levels, Grids, Columns, Floors and Walls. The tool works as intended, based on the feedback of users and their own experience. The person that led the product's development was a structural engineer with many years of experience and then many years of structural engineering software design.
All software development defines a scope of work, identifying a problem to solve, and then works to reach their goals. It's very much like architecture and engineering projects. No building gets built without some misunderstanding or compromise. The way it works is precisely how they perceived the needs of the problem they were trying to solve. Looking back with 14 years of experience is naturally going to provide nearly everyone with a different perspective.
What you describe as insane was apparently not insane enough for Autodesk and it's staff to spend a lot of money on a brand new product that included these features as they are.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
