Author Topic: Titlesheets as xresfs  (Read 5347 times)

0 Members and 1 Guest are viewing this topic.

Daniel J. Ellis

  • Swamp Rat
  • Posts: 811
Titlesheets as xresfs
« on: March 13, 2010, 04:11:25 AM »
Running through our roughly annual review of CAD standards and practices, and some one suggested using xrefs for titlesheets, but he wasn't sure how this would work in practice.

I know several of the guys her ehave mentioned making theier titlesheets this way: how does this work?

Information on our titlesheets (ATM) is job description, drawing description, drawing number, date, client logo, and drawn initials.
===
dJE

Krushert

  • Seagull
  • Posts: 13679
  • FREE BEER Tomorrow!!
Re: Titlesheets as xresfs
« Reply #1 on: March 13, 2010, 10:04:33 AM »
You mean Title Blocks.  Yes we xref our TBs and love it.  You have to seperate what data/info is constant for every drawing to drawing and what is unique for every drawing.  The only growing pain is if you share your drawings with outside sources.  You have to remember to be sure to include your title block.  If you use professional stamps then I would suggest xrefing that to the source TB as an nested xref.  Then you have to detach that when you share your files.  But that is a simple process with Etransmit function. 
I + XI = X is true ...  ... if you change your perspective.

I no longer CAD or Model, I just hang out here picking up the empties beer cans

Bob Garner

  • Guest
Re: Titlesheets as xresfs
« Reply #2 on: March 13, 2010, 10:15:36 AM »
Ditto to everything Krushert said.  Our office doesn't xfef titleblocks but our corporate office does for large jobs where making any changes to 150 titleblocks would be a pain.  I don't like to xref titleblocks for small jobs because, well, I need to simplicate things and I'm always losing my xrefs.

sinc

  • Guest
Re: Titlesheets as xresfs
« Reply #3 on: March 13, 2010, 11:03:54 AM »
We've been putting our titleblocks in paperspace, and then use the Sheet Set Manager to change things like job name, issue date, etc.  However, we do not have a client's logo in our title block...  I don't think the SSM will let you do something like that.

JCTER

  • Guest
Re: Titlesheets as xresfs
« Reply #4 on: March 13, 2010, 04:40:09 PM »
We copy a title block from our standard files into the folder for each job.  Xref'd into each working drawing.

The only thing that's specific to our job is the revision level, revision description, rev date, and initials applicable to the revision.

Everything is stored in the title block as a field, if it changes drawing-to-drawing, and the field references somewhere safe for it to change each time.

mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Titlesheets as xrefs
« Reply #5 on: March 13, 2010, 08:59:35 PM »
you will want to explore

fields for the SET, and fields for the Sheet...consultant logo(s), can be a block with or without visibility states to turn yours, or theirs on as needed.
« Last Edit: March 15, 2010, 07:24:21 PM by mjfarrell »
Be your Best


Michael Farrell
http://primeservicesglobal.com/

Daniel J. Ellis

  • Swamp Rat
  • Posts: 811
Re: Titlesheets as xresfs
« Reply #6 on: March 14, 2010, 05:31:07 AM »
How much time saving does it represent?

Our sheet set will normally be limimted to about a dozen sheets, very often at different paper sizes.

Presumably that would potentially leave us with three or four different xrefs to deal with...
===
dJE

Krushert

  • Seagull
  • Posts: 13679
  • FREE BEER Tomorrow!!
Re: Titlesheets as xresfs
« Reply #7 on: March 15, 2010, 09:47:37 AM »
How much time saving does it represent?
 huge time savings.  My Client here last week could not make up their mind on what they wanted the rev block to say for the as-built drawings for 118 sheets.  (All I can say is that they are MEP folks - Need I say anymore   :-D)   Change 3 pieces of text in one file - three different times.  How long does that take?  Now take that same time and multiply times a 118 times.  The kicker is disruptions during the changing 118 sheets and then you forget what and where you were and miss a sheet or two.  Then you got phone calls from the client whining and what not. I will almost anything to reduce errors especially simple one like this.

Our sheet set will normally be limited to about a dozen sheets, very often at different paper sizes.

Presumably that would potentially leave us with three or four different xrefs to deal with...
Then this could be a more hassle that it is worth with having that many TB xrefs and so few sheets.  Personally I would still do it for the reasons mention above.   But to each their own.  

My suggestion is to try it for a project or two.  We tried as an experiment and we like it.
I + XI = X is true ...  ... if you change your perspective.

I no longer CAD or Model, I just hang out here picking up the empties beer cans

mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Titlesheets as xrefs
« Reply #8 on: March 15, 2010, 10:22:43 AM »
Given the number of Sheet Sizes...it might be a toss up if Xreffing them into your files will save any time; unless the title blocks can or do scale proportionately to fit the various sized sheets.
However, it think that even just using Fields, and one Title Block per sheet, most likely will Still save you some time.
« Last Edit: March 15, 2010, 07:24:33 PM by mjfarrell »
Be your Best


Michael Farrell
http://primeservicesglobal.com/

JCTER

  • Guest
Re: Titlesheets as xresfs
« Reply #9 on: March 15, 2010, 10:29:51 AM »
Just a thought, but what if your xref'd title block had every size you need, in that one xref?

That way, when you are in your layout tab, you'd have 3 title blocks showing (for 3 dif sizes) and you'd just have to create your viewports and what not in the right one.  Maybe even use XCLIP to 'hide' the non-relevant sizes?

It would affect your plotting situation, a bit, but could be an easy workaround.  You'd just have to insert the xref such that the desired title block had it's base point at 0,0, or just use "Window" to select the plot area, and have defined page setups for each size.

That way you could have all the same information, etc, in each title block, and only one file to insert.  May create need for a little adjustment to standard practices, but I don't think it'd require much, and would still be a big increase in efficiency.

You'd probably just have to have an empty area in your title block for client logos and what not, and just insert the proper one into the xref file on a per-job basis.  Maybe make it a dynamic block for easy swapping/switching.

mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Titlesheets as xrefs
« Reply #10 on: March 15, 2010, 10:32:10 AM »
I do not think that If the titleblock is set correctly one MUST plot by WINDOW an not by Layout...every office whose standards I've helped develop uses LAYOUT not window when plotting from layouts.
« Last Edit: March 15, 2010, 07:24:47 PM by mjfarrell »
Be your Best


Michael Farrell
http://primeservicesglobal.com/

JCTER

  • Guest
Re: Titlesheets as xresfs
« Reply #11 on: March 15, 2010, 10:44:13 AM »
I do not think that If the titleblock is set correctly one MUST plot by WINDOW an not by Layout...every office whose standards I've helped develop uses LAYOUT not window when plotting from layouts.

Didn't say they must...

Also we're not talking about a typical situation.  How many offices have you helped that have multiple title blocks in one layout?  I was suggesting something very nontypical, so it's not too surprising if nontypical process would be employed...  :roll:

mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Titlesheets as xrefs
« Reply #12 on: March 15, 2010, 10:52:36 AM »
I do not think that If the titleblock is set correctly one MUST plot by WINDOW an not by Layout...every office whose standards I've helped develop uses LAYOUT not window when plotting from layouts.

Didn't say they must...

Also we're not talking about a typical situation.  How many offices have you helped that have multiple title blocks in one layout?  I was suggesting something very nontypical, so it's not too surprising if nontypical process would be employed...  :roll:

It might be NON typical to have multiple title blocks in one XREF, however there really doesn't seem to be a need to keep veering away from the path of normal(typical) to implement this solution.  Further the closer to normal and typical you keep this 'solution'; the easier it will be for the users to adapt to, and actually use the 'solution' otherwise it becomes just another problem to work around.
« Last Edit: March 15, 2010, 07:25:01 PM by mjfarrell »
Be your Best


Michael Farrell
http://primeservicesglobal.com/

JCTER

  • Guest
Re: Titlesheets as xresfs
« Reply #13 on: March 15, 2010, 10:55:22 AM »
I do not think that If the titleblock is set correctly one MUST plot by WINDOW an not by Layout...every office whose standards I've helped develop uses LAYOUT not window when plotting from layouts.

Didn't say they must...

Also we're not talking about a typical situation.  How many offices have you helped that have multiple title blocks in one layout?  I was suggesting something very nontypical, so it's not too surprising if nontypical process would be employed...  :roll:

It might be NON typical to have multiple title blocks in one XREF, however there really doesn't seem to be a need to keep veering away from the path of normal(typical) to implement this solution.  Further the closer to normal and typical you keep this 'solution'; the easier it will be for the users to adapt to, and actually use the 'solution' otherwise it becomes just another problem to work around.

You have a better idea for how to implement an xref'd title block where multiple sheet sizes can come into play?

sinc

  • Guest
Re: Titlesheets as xresfs
« Reply #14 on: March 15, 2010, 11:01:31 AM »
I do not think that If the titleblock is set correctly one MUST plot by WINDOW an not by Layout...every office whose standards I've helped develop uses LAYOUT not window when plotting from layouts.

The problem we have with LAYOUT is that it can create issues with Page Setup Overrides.  So we use "Extents" a lot instead.  This has the drawback that we can't have any clutter laying around our layout in paperspace, but we typically have no clutter there anyway, so it works out.