| ARCH 367/667 Working Drawings Notes, week 5 Jonathan Ochshorn: contact | homepage | fall 2007 index for ARCH 262/562 | past and current indexes for ARCH 367/667 Drafting conventions: notations, terms, and abbreviationsBased on National CAD Standard 3.1
NotationsPDF pp. 366-371Notations, or notes, are needed on working drawings where the graphic images, by themselves, cannot convey the required information. A notation may apply to the whole set of drawings (or documents), to a particular discipline (e.g.., architectural drawings and specifications), or may only apply within an individual sheet or drawing. Some guidelines for notations: Identification of spaces:
Identification of objects:
Cross-referencing: The organization of information begins with the floor plan. From this drawing, we reference sections, elevations, interior elevations, large-scale plans, and plan details. Avoid redundancy by keeping notations in a single location (e.g., in a detail, but not in the section). The idea of a mock-up set (see week 8) helps. Cross-reference other drawings where such information is helpful, but be somewhat selective, avoiding obvious cross-references (as in: see elevation for position of window in facade...)
As mentioned previously, identify each drawing and each sheet with a unique identifier. The cross-referencing can continue, if necessary, with additional details keyed in from the "detail" itself.
Terms and abbreviationsPDF pp.427-605Use abbreviations only to improve clarity, or to save time and space: do not abuse the privilege. Spell out words whenever possible. In general, do not abbreviate any word of 5 letters or less, except where useful for formatting schedules. Some abbreviations refer to multiple words. This is OK where the variations occur in different disciplines, but not OK if it is likely to cause confusion within a single discipline. In the latter case, spell it out. Either reference the UDS [uniform drawing system] Terms and Abbreviations, or create your own list derived from the UDS. Note that the UDS also contains words that should not be used, often because a different word, or phrase, is preferred. So, drywall is superseded by gypsum board (GYP BD).
NotationsPDF pp. 801-Purpose of notations:
Types of notes: apply to entire work, show up on "G" sheets; need not be repeated subsequently on different drawings.
Appear on first, or "0"-series sheets (that is, general sheets containing symbols legend, notes, etc.: see week 2 notes) within a particular discipline, and do not duplicate general notes. They might, for example, contain references to the drawing conventions specific to a discipline. The example given in the UDS is:
Write such notes in the "imperative mood" as in recommended "specification" language: direct commands, requests, and prohibitions without the second-person "you" included. So, for example: "LABEL ALL DRAWINGS." Instead of, or in addition to, textual messages, reference keynotes identify graphic representations with specific specification sections. Example from the UDS is: 01 56 00.A01 - TEMPORARY DUST BARRIER TYPE 1. The last 3 characters are user-defined suffix and modifiers (A.01) which allow references of multiple keynotes within the same specifications section. See PDF p.814 for image example. These notes are indicated with a hexagonal symbol that contains the note's number inside and a leader from the hexagon that points to the item being described. An example would be a note that says: "ALIGN FACE OF NEW WALL WITH COLUMN CENTERLINE." Within the drawing itself, the hexagon symbol (with appropriate number inside) would then be used to identify applicable walls. In this way, the note itself does not need to be repeated over and over again. See PDF page 815. The first three are not directly linked to graphic representations; if they appear on the same sheet, they are ordered as shown above.
The language of notes:
If reference to the specifications is deemed useful, be specific, e.g., "SEE SPECIFICATION SECTION 08 10 09.13." Use capitalized, proportional, sans-serif, non-stylized fonts. First posted: 24 September 2007 | Last Updated: 24 September 2007 © 2007 J. Ochshorn. All rights reserved. |