Author Topic: Shell & Core vs T.I. (Read 7682 times)

cam-nav · « **on:** Dec 17, 2009, 17:14:48 PM »

How do you handle shell and core drawings versus tenant improvement drawings.

Some here say they like the TI in one drawing and others say they like separate drawings for TI.

I for one am in favor of the latter, because we have an export feature that extracts drawing item weights and trying to keep the items separated would be difficult if the two were lumped into one drawing.

Stuff to keep in mind if you used to do things a certain way for years it might be wise to think of new ways to keep drawings organized. Unless MAP can incorporate a way for this to be handled as separate entities.

The ones here infavor of keeping all in one drawing say that xreffing new drawings in their drawings would be alot of extra not needed work.

Any comments, ideas or work arounds?

tnbndr · « **Reply #1 on:** Dec 17, 2009, 18:00:32 PM »

Dave:
What I would do is for each TI xref in the Shell & Core drawing so you have the background of the building (grey out duct & piping as existing). Then xref in the TI walls and draw the duct and piping. I would do this for each TI to keep them separate.
Then if the owner wants a composite you can create a drawing the xrefs in each TI plus the Shell & Core.
We would do it this way simply because each TI would be a different job number and we save our drawings in folders by job number. Reason I would not want it all in one drawing is simply trying to distinquish new work from existing for the installers.

VirtualPilot · « **Reply #2 on:** Dec 18, 2009, 02:17:52 AM »

Unless you can assign individual layers to all the ducts that belong to each tenant...

Such as layer "TENANT 01 - SUPPLY DUCT" and so on...

I treat Tenant work as new work, so it will go to it
s own new job folder...

If at the end, someone for some odd reason would like to know what the entire job runs, then you can insert everything into a massive file and get the report from there...

VirtualPilot · « **Reply #3 on:** Dec 18, 2009, 02:18:52 AM »

I should off read Dennis answer....LOL

cadbyken · « **Reply #4 on:** Dec 18, 2009, 02:21:39 AM »

Quote from: VirtualPilot

I should off read Dennis answer....LOL

Ahh, padding your post count?

tnbndr · « **Reply #5 on:** Dec 18, 2009, 05:29:21 AM »

Quote

I should off read Dennis answer....LOL

Great minds think alike!

Would have saved you some typing though.

CaddMan22 · « **Reply #6 on:** Dec 18, 2009, 18:44:36 PM »

Dave
I also keep them seperate as we also file by job #. I also have created (2) new services. Existing & Demo, so you can Isolate even further if needed.

cam-nav · « **Reply #7 on:** Dec 18, 2009, 19:36:10 PM »

Well the tenant work is the same job number or else we would have separate files.

I just wanted them separate for the reporting purposes and I know there are other reasons to have them in their own drawings too. Just wanted to get some other opinions about this.
I also think the tenant work needs to be separate files even if it is the same job number, just to keep the work separated, we do have different cost codes for tenant work.