Xrefing to a detail library

Hopefully someone can explain the benefit of this, if thee is one:

I interviewed at a structural engineers' firm and took a drafting test,
when it came time to add a detail I was told to xref a detail that was
in the detail library folder. My first response was shouldn't your xref
be in the job folder, what happens in a few years when you update the
detail or have to plot a set from a computer not on your network or you
overhaul your network?

Am I missing something. I don't have alot of experience with xref's
other than my titleblock. and maybe sometimes my wall layout.

TIA.
Jeff

 

In regards the xref being located in the project folder, no, it doesn't have
to be located there. The most common way of addressing the path issue is to
use a relative path when inserting. There are numerous methods to reset the
xref pathing.

Concerning xrefing a detail.... I can see where some businesses that would
want the most current detail being xrefed in when producing/plotting a
drawing. I currently work for a structural engineering firm and while we do
use xrefs (our foundation drawing is xrefed into the second floor, etc.) we
do not xref in details, they are inserted. Two years from the date of issue
if we print another copy of a particular project we want to see the detail
as it was drawn at the time the drawing was issued and sealed.

 

I'm not sure why they are xrefing the details either, I have always
inserted the detail as a block to ensure that the drawings stays the way
it was drawn. I would never xref something that might get updated down
the road.

what is a relative path? I'm using A2Ki. I thought I was only given the
option to retain the path or not. I have always chosen not to. since my
xref's were in my job folder.

Jeff

 

Relative path is the basically the path to the file, relative to the drawing
location, rather than the full path from the root. So if your xref is
located in a subfolder to the drawing location, you can move the folders to
another computer or drive and AutoCAD will be able to locate the xref
because it looks in the subfolder "relative" to the current drawing .

 

IMHO if xrefing a detail it should be in the job folder where it will be
picked up first, else as you said I would *insert it. Unless you can be
sure that the detail number will not change xrefing could be dangerous as it
could be updated without your knowledge.

 

We have a series of "standard details" held in a network directory. These details are static, and require formal procedures for updating. Thses are xref'd into project drawings as needed.

Each project may have a set of "custom" general details on a set of drawings that are displayed on a project detail sheet. Then each assembly/facility may have individual specific details. These are not xref'd.

 

That's a huge problem. We don't xref typical details and the like because of
that reason and others:
1. That detail may not suit the current project and may need to be
altered slightly (maybe a dmiension changes, or some reinforcing changes or
is taken out). You can't do that witout effecting all the other places that
xref that detail.
2. The detail may not be up to code or may not meet the design basis for
that project. See note 1
3. Inserting a fresh detail each time forces a review of the detail for
reasons mentioned in note 1 & 2.
4. Before relative paths, chainging a server drive letter would've cause
major headaches
5. Terminology changes over time with new design criteria (threaded rod
anchor bolts become threaded rod anchors.) See notes 1,2,&3.
6. Maybe your office changes from ctb to stb at some point. See note
1,2, & 3.

There's probably more.

 

Seems like a bad idea to me.

 

Thanks, for all the info. I thought It was a bad idea, but since I don't
use xref's that much I thought I might be missing something.

I think I understand what a relative path is, I finished a subdivision
project that another drafter started, he had a project forlder and
inside that folder were folders for each floor plan, all the details and
all the notes. The detail sheets for each plan were xref'd to the
detail folder.

In the engineers office the plans were on the work station and the
details were on the server.

Thanks,
Jeff

 

I've worked in offices where certain details were xref'd in from a central detail library. It only really works for standardized roll-out type work like retail or turn-key stuff. All of the pitfalls from the other posters are valid, but most can be dealt with by an attentive project manager and non-lazy draftsman.

After a project was completed, the xref's were bound into the set so that the original issue was preserved (should the detail ever be modified in the future.).

Certainly not the best way to work, nor a common way to work, but I've seen more dangerous things in some offices.

 

Jon's comments all good. One to add: Opening an old drawing to plot or revise may display revised xref'd details that weren't in the origina set. Lawyers love this practice.....

OC.'s comments about xref'd general standard details is valid and like any "system", requires control and maintenance.

Hope they bind the xrefs at the end of the project