another stb question

[Anonymous]

Hi,

I have yet another question on .stb files. So far I have only worked with
.ctb and am trying to understand the advantages of .stb. I have read thru
the latest discussion here on this subject. I didn't see my primary question
answered.

How do multiple disciplines on a project conform to a single .stb as per
client (who is controlling final plotting) and still have the ability to
assign lineweight at the layer level? In other words, the client isn't going
to want a different plot style for each sub when it comes time to print the
entire package.

Thanks!

[Anonymous]

J,

I don't see an easy way to do this, and it has nothing to do with stb vs.
ctb. I has more to do with in-house office standards. Everyone's will likely
be different. Different disciplines use different lineweights to represent
the same information for different reasons. So, there's no magic bullet to
hit this target as I see it. To have everyone use the same stb would be
nice, but it's just not realistic. It would require retooling everyone's
standards to meet at some common meeting ground (NCS maybe?) which isn't
likely to happen ever.
So, while you can send someone your ctb or stb files so they can print like
you intend for your drawings to plot, unless you and your colleagues all
want to set up some standard (or adopt one like the NCS) it just won't
happen and isn't realistic.

At least, not in any way I can see it happening.

Robert Grandmaison


"J McCarl" wrote in message
news:BD25C36BBBE0CB1E1871513A3E124552@in.WebX.maYIadrTaRb...
> Hi,
>
> I have yet another question on .stb files. So far I have only worked with
> .ctb and am trying to understand the advantages of .stb. I have read thru
> the latest discussion here on this subject. I didn't see my primary
question
> answered.
>
> How do multiple disciplines on a project conform to a single .stb as per
> client (who is controlling final plotting) and still have the ability to
> assign lineweight at the layer level? In other words, the client isn't
going
> to want a different plot style for each sub when it comes time to print
the
> entire package.
>
> Thanks!
>
>

[Anonymous]

Thanks for the reply. I agree it is difficult. I can bend my mind around
creating a multiple discipline .ctb file by setting standard lineweights per
color to cover more than one discipline, but can't figure how it could work
for .stb-if you wanted to use lineweight by layer. If you didn't? I need to
go work with .stb.
Thx again.

Robert Grandmaison wrote in message
news:575F262991B4DE8AB5E9391AE568A5B4@in.WebX.maYIadrTaRb...
> J,
>
> I don't see an easy way to do this, and it has nothing to do with stb vs.
> ctb. I has more to do with in-house office standards. Everyone's will
likely
> be different. Different disciplines use different lineweights to represent
> the same information for different reasons. So, there's no magic bullet to
> hit this target as I see it. To have everyone use the same stb would be
> nice, but it's just not realistic. It would require retooling everyone's
> standards to meet at some common meeting ground (NCS maybe?) which isn't
> likely to happen ever.
> So, while you can send someone your ctb or stb files so they can print
like
> you intend for your drawings to plot, unless you and your colleagues all
> want to set up some standard (or adopt one like the NCS) it just won't
> happen and isn't realistic.
>
> At least, not in any way I can see it happening.
>
> Robert Grandmaison
>
>
> "J McCarl" wrote in message
> news:BD25C36BBBE0CB1E1871513A3E124552@in.WebX.maYIadrTaRb...
> > Hi,
> >
> > I have yet another question on .stb files. So far I have only worked
with
> > .ctb and am trying to understand the advantages of .stb. I have read
thru
> > the latest discussion here on this subject. I didn't see my primary
> question
> > answered.
> >
> > How do multiple disciplines on a project conform to a single .stb as per
> > client (who is controlling final plotting) and still have the ability to
> > assign lineweight at the layer level? In other words, the client isn't
> going
> > to want a different plot style for each sub when it comes time to print
> the
> > entire package.
> >
> > Thanks!
> >
> >
>
>

[Anonymous]

One other option would be to draw in your current standard and then convert
to a common standard at the end of the project by using the CAD Management
Extension that AutoDesk offers. It would require the initial setup but as
long as everything was drawn bylayer to begin with the transition shouldn't
be that bad.

"J McCarl" wrote in message
news:05AD9EE9A10D6F7D9B36CC414A0E31E0@in.WebX.maYIadrTaRb...
> Thanks for the reply. I agree it is difficult. I can bend my mind around
> creating a multiple discipline .ctb file by setting standard lineweights
per
> color to cover more than one discipline, but can't figure how it could
work
> for .stb-if you wanted to use lineweight by layer. If you didn't? I need
to
> go work with .stb.
> Thx again.
>
> Robert Grandmaison wrote in message
> news:575F262991B4DE8AB5E9391AE568A5B4@in.WebX.maYIadrTaRb...
> > J,
> >
> > I don't see an easy way to do this, and it has nothing to do with stb
vs.
> > ctb. I has more to do with in-house office standards. Everyone's will
> likely
> > be different. Different disciplines use different lineweights to
represent
> > the same information for different reasons. So, there's no magic bullet
to
> > hit this target as I see it. To have everyone use the same stb would be
> > nice, but it's just not realistic. It would require retooling everyone's
> > standards to meet at some common meeting ground (NCS maybe?) which isn't
> > likely to happen ever.
> > So, while you can send someone your ctb or stb files so they can print
> like
> > you intend for your drawings to plot, unless you and your colleagues all
> > want to set up some standard (or adopt one like the NCS) it just won't
> > happen and isn't realistic.
> >
> > At least, not in any way I can see it happening.
> >
> > Robert Grandmaison
> >
> >
> > "J McCarl" wrote in message
> > news:BD25C36BBBE0CB1E1871513A3E124552@in.WebX.maYIadrTaRb...
> > > Hi,
> > >
> > > I have yet another question on .stb files. So far I have only worked
> with
> > > .ctb and am trying to understand the advantages of .stb. I have read
> thru
> > > the latest discussion here on this subject. I didn't see my primary
> > question
> > > answered.
> > >
> > > How do multiple disciplines on a project conform to a single .stb as
per
> > > client (who is controlling final plotting) and still have the ability
to
> > > assign lineweight at the layer level? In other words, the client isn't
> > going
> > > to want a different plot style for each sub when it comes time to
print
> > the
> > > entire package.
> > >
> > > Thanks!
> > >
> > >
> >
> >
>
>
>

[Anonymous]

The lineweights you assign within the .stb plot style can override the ones
you assign to layers or objects. That way you can just assign a different
.stb plot style to each plot / layout.

-Raj


"Darek Olson" wrote in message
news:73B9E3EBD944FDB59448AF38BF58B0A4@in.WebX.maYIadrTaRb...
One other option would be to draw in your current standard and then convert
to a common standard at the end of the project by using the CAD Management
Extension that AutoDesk offers. It would require the initial setup but as
long as everything was drawn bylayer to begin with the transition shouldn't
be that bad.

"J McCarl" wrote in message
news:05AD9EE9A10D6F7D9B36CC414A0E31E0@in.WebX.maYIadrTaRb...
> Thanks for the reply. I agree it is difficult. I can bend my mind around
> creating a multiple discipline .ctb file by setting standard lineweights
per
> color to cover more than one discipline, but can't figure how it could
work
> for .stb-if you wanted to use lineweight by layer. If you didn't? I need
to
> go work with .stb.
> Thx again.
>
> Robert Grandmaison wrote in message
> news:575F262991B4DE8AB5E9391AE568A5B4@in.WebX.maYIadrTaRb...
> > J,
> >
> > I don't see an easy way to do this, and it has nothing to do with stb
vs.
> > ctb. I has more to do with in-house office standards. Everyone's will
> likely
> > be different. Different disciplines use different lineweights to
represent
> > the same information for different reasons. So, there's no magic bullet
to
> > hit this target as I see it. To have everyone use the same stb would be
> > nice, but it's just not realistic. It would require retooling everyone's
> > standards to meet at some common meeting ground (NCS maybe?) which isn't
> > likely to happen ever.
> > So, while you can send someone your ctb or stb files so they can print
> like
> > you intend for your drawings to plot, unless you and your colleagues all
> > want to set up some standard (or adopt one like the NCS) it just won't
> > happen and isn't realistic.
> >
> > At least, not in any way I can see it happening.
> >
> > Robert Grandmaison
> >
> >
> > "J McCarl" wrote in message
> > news:BD25C36BBBE0CB1E1871513A3E124552@in.WebX.maYIadrTaRb...
> > > Hi,
> > >
> > > I have yet another question on .stb files. So far I have only worked
> with
> > > .ctb and am trying to understand the advantages of .stb. I have read
> thru
> > > the latest discussion here on this subject. I didn't see my primary
> > question
> > > answered.
> > >
> > > How do multiple disciplines on a project conform to a single .stb as
per
> > > client (who is controlling final plotting) and still have the ability
to
> > > assign lineweight at the layer level? In other words, the client isn't
> > going
> > > to want a different plot style for each sub when it comes time to
print
> > the
> > > entire package.
> > >
> > > Thanks!
> > >
> > >
> >
> >
>
>
>