View labeling on multi sheet drawing

[marshell]

Is there a section of any ASME specification that talks about how views on multi sheet drawings should be labeled? I am not referring to cross referencing for things like sections or details, but on complicated drawings where the views may be repeated on subsequent sheets with different features dimensioned. (For example, a machined electronic enclosure where sheet 1 may have the box dimensions, and sheet 2 may contain similar views but dimension the holes). Does there need to be some sort of cross reference to the views? Maybe one view labeled "top" on all sheets, or some other relating verbiage?

Thank you,

 

[Belanger]

I don't know the answer offhand. But I think the pertinent standard may be ASME Y14.3.

John-Paul Belanger
Certified Sr. GD&T Professional
Geometric Learning Systems

 

[3DDave]

I think there is no allowance for that. Instead, create uniquely named views and under the view on the first sheet include a notation that lists the other views, the sheets they are on, and if you are feeling kind, the function for the view.

Such as:

SEE VIEW B, SHEET 4 - BOX MTG HOLE DETAILS
SEE VIEW C, SHEET 5 - BOX WELDING CALLOUTS

 

[Tunalover]

I agree with Belanger. Get yourself ASME Y14.3 and a good drafting manual like the Genium Publishing DRM. Personally I don't provide pointers to where the views are located. I just put the views on subsequent sheets and require the reader to find them. This makes the drawing less susceptible to errors when the time comes to move views around to fit in other views and/or to delete views.


Tunalover

 

[ewh]

Here we have done away with labels such as "TOP", BOTTOM", etc as they are usually arbitrary as far as the fabricator is concerned.
If we need to reference the same detail more than once, we always add a descriptor under the label so that the reader can easily understand that, while it may be a redundant view, the information shown is not. If it is a redundant projected view, a definition hinge line is added to provide identification and only the additional projection is labelled (since it would be in effect a "removed view").Ideally each view not in direct projection should have a unique identifyer.

"Know the rules well, so you can break them effectively."
-Dalai Lama XIV

 

[marshell]

Thank you all for the input. I have looked through Y14.100, 14.3, the latest Global DRM, and even looked through the GSFC Drawing Standard. Closest thing I found to mentioning it was from the GSFC manual that stated "A view of another view shall not be used, unless necessary for clarification" but no instruction if you do it.

I guess it all comes down to doing whatever is clear and understandable to the end user. If the view is distinct enough that it would not be confused with another, an identifier may not be needed, bit if it could be confused with another view... ID it. It appears how this identification is to be done, is not defined, so that leave it open to whatever each company wants to do.

Thank you,

 

[KENAT]

I've repeated removed views before when necessary. e.g. I'll have view A-A multiple times. It's fundamentally the same view just with different features dimensioned or what have you.

If in conversation or on a quality report or somewhere you need to be able to distinguish then use the zone & if applicable sheet number to achieve this.

Posting guidelines faq731-376

http://eng-tips.com/market.cfm?

(probably not aimed specifically at you)
What is Engineering anyway: faq1088-1484​

 

[marshell]

I did come across something in 14.3, section 6.1 that may work, though I do not believe I have seen it in different worlds. It appears it is stating the use of a coordinate system may be used. It states "The coordinate system may be used to indicate view orientation, and to establish the relationships between views. When complex features need to be related in the drawing, and pictorial views are inadequate, orthographic views, saved views in the model, or a design model shall be used." That would give the user a relationship of a view if a coordinate system is shown on the applicable views.

Kenat. I have used what you are referring to also in the past. Unfortunately it appears to not be allowed per the ASME requirements, so I will have to stay clear of that method. Per ASME Y14.3 Section 6.5 Cross-Referencing Views "View identification letters shall not be repeated on more than one view. Only one set of alpha characters shall be
used per drawing for naming views of all types without repeating the same letters on more than one view. For example, for a drawing consisting of three named views
of either the same or different types (a section view, a removed view, and a detail view) the views would be named SECTION A-A, VIEW B-B, and DETAIL C."

Thanks.

 

[KENAT]

My point marshell is that it is the same 'view'. The geometry etc. shown is not any different.

Posting guidelines faq731-376

http://eng-tips.com/market.cfm?

(probably not aimed specifically at you)
What is Engineering anyway: faq1088-1484​

 

[ewh]

I agree with KENAT (again)... While it may not be the same view placement, it is essentially the same view.

"Know the rules well, so you can break them effectively."
-Dalai Lama XIV

 

[MikeHalloran]

In days of yore, I'd have redrawn the whole mess on a larger sheet so that all relevant/related views are accessible to the reader at the same time.

Now, since everything is printed at B size or smaller, related views must be on a different sheet, and I'd do every damn thing possible to help the reader navigate the mess, regardless of what any standard defines as minimal.



Mike Halloran
Pembroke Pines, FL, USA

 

[KENAT]

Mike, I still go to larger sheet first and extra sheets only after my E sheet is over flowing.

Having all the views laid out on a single sheet is SO much easier to read the drawing - even on the computer screen to me.

If users want to cheap out and not have a plotter they can also get magnifying glasses for all drawing users.;-)

Posting guidelines faq731-376

http://eng-tips.com/market.cfm?

(probably not aimed specifically at you)
What is Engineering anyway: faq1088-1484​