Monday, January 30, 2012

Multi-Disciplinary View Coordination

Back in 2008 I posted a response to an AUGI thread which contains tips that are still relevant to this day and might be unknown to some users. So I thought of echoing it out here.

The main question was about what the best process is to ensure that view extents (ex: plans) are coordinated between different sheets and different disciplines. The discussion then centered on Scope Boxes:

“When you create a scope box, it's just like drawing a rectangle in plan. You can specify a height too (that's why it's a scope box and not rectangle!). Make sure you give it a good descriptive name (Ex: Area 'A'). You can then go to a plan view's properties and under Extents, assign the Scope Box that defines the area you want to see. The crop region will automatically coincide with the scope box. In fact to change the crop region, you now have to modify the scope box by moving the drag handles and the crop region will follow.
So for a large project, the workflow would be as follows:

  1. In an overall plan view, place scope boxes to "chop" your plan in meaningful pieces so it fits on your drawing sheets. Name them accordingly and place any matchlines and view references here;
  2. Create dependent views (let's say you have 5 plan areas....create 5 dependent views and we'll assign them to the 5 scope boxes created in step (1));
  3. Go to each dependent view, name it something meaningful (ex: Area 'A') and assign the appropriate scope box to it. You can turn off scope box visibility to remove clutter as you typically overlap scope boxes so you can show some context (you have to do this to properly use matchlines);
  4. If you want to make changes to the crop region, always go to the parent view, turn on scope boxes or use the Reveal Hidden Elements button (if scope boxes were hidden, they'll become visible in magenta) can now modify them and when you're done, click on the Reveal Hidden Elements button once again and they'll go away or hide the category. Your crop regions would have automatically followed the changes in your scope boxes;
  5. The above is done typically by Architectural. Now consultants just link in as usual, they set a plan view that shows the scope boxes, match lines and view references (perhaps set to "By Linked View" to facilitate this) and copy all these elements into their project file. You do that by tabbing until the object in the link is highligted, then copy and paste in the same location*. Now you just need to carry on from step (2) once you have the same scope boxes residing in your project.”

* As Steve Stafford noted in the thread, scope boxes tend to paste exactly in the same spot automatically, regardless of the paste option picked.



Alex said...

Thanks for the explanation of scope boxes.

mortenmr said...

But why does scope boxes show as an unordered list? Really confusing, irritating and makes it impossible to use for larger projects with potentially a lot of boxes...

Anonymous said...

Great tip... thanks.

Anonymous said...

Thanks a million for this info, worked a treat on a big project we are working on at the moment.

Dave Baldacchino said...

mortenmr, I think they display by order of creation instead of by name. Probably not ideal, but it's not the first drop-down I see sorted that way.

Post a Comment