Replicating Views in discipline.

[Cathy Hadley]

Lets say an Architect has 200 Views of the project. He wants the Consultants to set up their Views in the same way. (I'm thinking crop regions and callouts, duplicate views, etc.. ?) The consultants in ACAD are used to just opening up those dwgs... and each viewport is pre-set as the ARCH wants to see them.

In Revit they Link in the ARCH model and no views... Once the views are set up I know we can use view templates or Revit links to get the visibiltiy correct. I'm talking View Setup and Sheet Layout ?

How would you go about creating all these views? I considered opening up the ARCH MODEL and then deleting all geometry but then phew you'd have to clean up each view of unwanted ARCH annotation... that would suck... I've been search AUGI and white papers and don't see anything...

How are consultants handling this...? Am I missing something obvious?

Cathy

[Cathy Hadley]

Hum... no takers.

This was the first question asked in my Class ... The MEP guys want the same sheet layout as the ARCH has... ? i.e. A101.1 wants to become M101.1 ?

How are you doing it today?

[patricks]

hmm interesting question. It would be nice if the Copy/Monitor tool could copy sheets and views as you wanted by selecting them.

[Bruce C. Olson]

The MEP guys want the same sheet layout as the ARCH has... ? i.e. A101.1 wants to become M101.1 ?

How are you doing it today?

I sure need to know how to do this!!!

Bruce

[Cathy Hadley]

The approach we ended up taking was to start the MEP model by opening up the Arch model... deleting all the geometry, which left the sheets & view, etc... then link back in the arch's model. Then Transfer project standards from an MEP template...

I think some things are still having to be manually updated, like filters, etc... but on the whole it seems to have worked.

[Bruce C. Olson]

The approach we ended up taking was to start the MEP model by opening up the Arch model... deleting all the geometry, which left the sheets & view, etc... then link back in the arch's model. Then Transfer project standards from an MEP template...

Yea I tried that, but because the Arch model is a Central file, and I'm a one-man band, I end up with a lot of grec that I don't need if I create my model without worksets. Also, the model was huge, about 200MB, so my poor XP machine that can only show 2.5GB was falling apart.

That I'll solve with a new Vista 64bit box, but it still was a lot of hassle.

[dbaldacchino]

Cathy, we use scope boxes to define the plan areas. So our in-house structural guys copy those scope boxes into their file (through our linked Arch project....tab, select, copy & paste). Once they're in their project, they just set their respective dependent views to the appropriate scope box. The crop regions will match exactly those in the Architectural project. MEP consultants would also do the same.

[mwiggins121466]

dbaldacchino,

I would like more information about this. I also link in the architectural but I do not see any scope boxes that I can copy. I do have vv in the link set to custom with the linked view set to the corresponding arch view. Might I be missing something?

TIA

[dbaldacchino]

Margaret, the Architectural guys/gals need to use scope boxes in order for you to be able to re-use them by copying them into your project. You would need to talk to them about this. I think it's a good method and has worked great for us. Once they start using them in projects and assign certain scope boxes to certain plan views to adjust the crop regions, you will be able to copy and use them in the same fashion in your project. Your crop regions will adjust to the extents of the scope box, and thus achieve view-extents consistency throughout all disciplines.

[mwiggins121466]

Dave,

Our architects do not use scope boxes currently. I spoke to them and they would like more information about them. Can they use them in conjunction with dependant views? What are the advantages to scope boxes? I need enough information to convince them it would be worth their time placing them.