Attachment_6__Appendix_E_01_35_13.20_00_Special_Project_Procedures_-_CAD.pdf

SECTION 01 35 13.20 00

SPFA3016-17-R-0033

SPECIAL PROJECT PROCEDURES- CAD

JOINT BASE SAN ANTONIO TEXAS

1. GENERAL

This Section covers the project requirements related to Computer Aided Drafting (CAD) files unique to Joint Base San Antonio, Texas.

1.1. REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to in the text by basic designation only.

UNITED STATES ARMY CORPS OF ENGINEERS

1.1.1. Engineer Research and Development Center (ERDC) / Information Technology Laboratory

(ITL)

1.1.2. ERDC/ITL TR-12-X: A/E/C CAD Standards Release 5.0, https://cadbim.usace.army.mil/CAD; Whole Building Design Guide, http://www.wbdg.org/ccb/AECCAD/aecstandardR5.pdf.

1.1.3. ERDC/ITL TR-12-1: CAD Drafting Standard, https://cadbim.usace.army.mil/CAD; Whole Building Design Guide, http://www.wbdg.org/ccb/AECCAD/aeccadstd.pdf.

JOINT BASE SAN ANTONIO (JBSA) PUBLICATIONS

1.1.4. JBSA Installation Design Guide July 2006, (http://www.samhouston.army.mil/dpw/) obtain pending updates by email usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil.

CITY OF SAN ANTONIO PUBLICATIONS

1.1.5. San Antonio Unified Development Code

http://library.municode.com/index.aspx?clientId=14228&stateId=43&stateName=Texas

1.2. PURPOSE

The purpose of the A/E/C CAD standard is to set a basic CAD standard to ensure consistent electronic deliverables within the DOD. These consistent deliverables are part of a comprehensive installation life-cycle management strategy. The A/E/C CAD standard sets a CAD standard specifically for the A/E/C disciplines of facilities development and civil works projects. The A/E/C CAD standard is utilized as tailored by this section.

1.3. SUBMITTALS

Attachment 6_ Appendix E_01 35 13.20 00 Special Project Procedures - CAD https://cadbim.usace.army.mil/CAD http://www.wbdg.org/ccb/AECCAD/aecstandardR5.pdf http://www.wbdg.org/ccb/AECCAD/aecstandardR5.pdf https://cadbim.usace.army.mil/CAD http://www.wbdg.org/ccb/AECCAD/aeccadstd.pdf http://www.samhouston.army.mil/dpw/) http://www.samhouston.army.mil/dpw/) mailto:usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil

DELIVERABLE FORMAT AND MEDIA FINAL and all INTERIM CAD submittals

1.3.1. All CAD files shall be provided in the Joint Base San Antonio target CAD system, AutoCAD 2010/2011 drawing format (.dwg). The Contractor shall ensure that all delivered CAD digital files and data (e.g., base files, reference files, block libraries) are compatible with the Government’s target CAD systems and operating systems, and adhere to the standards and requirements specified herein. NOTE: The term “compatible” means that data are in native digital format (i.e. dwg, pdf, docx, xlsx, etc.) and can be accessed directly by the target CAD system without translation, proxy errors, pre-processing, or post processing of the digital data files. It is the responsibility of the Con tractor to ensure this level of compatibility.

1.3.2. All CAD files shall contain the original vector line work (a scanned file placed in the cad file as an image is not sufficient). Any work done in a non- target CAD system must be translated by the Contractor to the target CAD System, and must be done in such a way that drawing functionality is maintained. For example the separation of the arrowhead from a leader line or dimension line is considered loss of functionality. All translation tables, mapping schemes, and original files (i.e. *.dwg files), and mapping tables, must be provided.

1.3.3. All project drawing sheets shall be submitted to the government with a matching CAD sheet file from which respective sheet was created from and a corresponding .pdf format file with matching file naming convention (i.e. if files A-101.dwg and C-101.dwg are submitted, files A- 101.pdf and C-101.pdf will need to be present within the submission).

1.3.4. All files shall be submitted on a DVD or CD, using the current government folder structure; Sheet files shall go in a sub-directory named “Sheets”, Model files (those referenced into the sheets) shall go in a sub-directory named “Support”, and PDF files shall be placed in a sub-directory named “PDF.”

1.3.5. Include metadata, control points, topographic, planimetric, and any additional supporting data.

1.3.6. Include other native formats if used – (i.e. MS Word, Excel, Access, Micro-station, etc.).

Email usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil for current versions required.

2. PRODUCTS

NOT APPLICABLE

3. EXECUTION

3.1. CAD FILES

NOTE: Page numbers refer to the A/E/C CAD Standard Release 5.0 unless stated otherwise.

3.1.1. The Contractor shall provide complete sheet files along with all model files referenced into these sheet files. For example, if a final design consists of 40 hardcopy sheets, then a minimum of 40 CAD sheet files and all external reference files (model CAD files, image files, etc.) used for the

Attachment 6_ Appendix E_01 35 13.20 00 Special Project Procedures - CAD

40 sheets shall be provided. There shall be no deviation from A/E/C CAD Standards Release 5.0, CAD drafting Standard, and this specification unless prior approval by 502 CES/CENMT has been officially obtained.

3.1.2. The Contractor shall provide all associated files used in the production of drawings (i.e.

plot styles, line types, external references, etc.) and be fully functional to reproduce submitted drawings. The preferred method of transmitting CAD files is to use the AutoCAD “e-Transmit” command onto a disk that is clearly marked with Project Name, Project Number, Type of Submission and date, as a minimum.

3.2. General instruction for drafting & plotting

3.2.1. Drafting shall be done in accordance with A/E/C CAD Standard Release 5.0 and CAD Drafting Standard. Plotting shall be done at a scale of 1:1 and utilizing the aecstdbandw named style table (aecstdbandw.stb). The Contractor shall not alter the assignments of the aecstdbandw.stb file;

Joint Base San Antonio will supply generic templates and the border sheet for use upon request by email to usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil.

3.2.2. Use of the available upon request templates and Sheet Set Manager (SSM) is preferred.

3.2.3. All drawings shall be in Imperial Units (inches and feet).

3.2.4. “Decimal and feet” units are only used for site plans.

3.2.5. All other drawings shall utilize “architectural and inches” units.

3.2.6. LOGOS: If the drawing is to be sealed, replace the 502 CES Logo in the top position of the title bar with the Seal. The Contractor may then place a Logo under the JBSA Logo located approximately half way up the title bar. If the drawing is not sealed, the Contractor may replace the 502 CES logo with the prime Contractor logo and place any subs below the JBSA Logo. In any case DO NOT ERASE the JBSA Logo.

3.3. Drawing File Organization

3.3.1. Chapter 2, page 6, Origin – 0, 0, 0 shall be used as the common origin point for all drawings – model, sheet, symbol, etc. unless otherwise approved. In the rare instance a different origin point is approved for a model file, a minimum of 3 registration points shall be incorporated into the file with reference to true state plane coordinate system (See Section 01 35 13.30 00 Special Project Procedures GIS for coordinate system).

3.3.2. Chapter 2, page 7-8, File Types & Drawing Sheet Assembly: All drawing graphics (lines, arcs, polygons, etc.) shall be in the model space (Model tab) of the model file.

3.3.2.1. All model files must be drawn at full scale (1:1).

3.3.2.2. All sheet files shall be a “ready-to-plot” CAD file.

3.3.2.3. The title block shall be externally referenced in the Layout tab (Paper Space) of each sheet file. All other drawings shall be externally referenced in the Model Tab of the sheet file.

3.3.3. Chapter 2, page 9-23, Electronic Drawing File Naming Conventions (Four mandatory fields).

3.3.3.1. Both model and sheet file naming convention shall begin using the same 10 to 12 character project code assigned by 502 CES. Project codes can be obtained by request to USAF JBSA 502 CES. usaf jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil.

3.3.3.2. A two character discipline designator shall follow the project code for both model and sheet files (The sheet file requires a level 2 designator).

3.3.3.3. The last two mandatory fields for model file names shall consist of a two character ‘model file type’ and a four character ‘user definable code’ (See page 10).

3.3.3.4. The last two mandatory codes consisting of three digits for sheet file names shall consist of a one digit ‘sheet type designator’ and a two digit ‘sheet sequence number’ (See page 22).

3.3.3.5. Sheet file names shall contain no user definable characters.

3.3.4. Chapter 3, page 25-28, Presentation Graphics

3.3.4.1. The template CAD files available upon request from the government utilize a named style pen table (drawing plot styles variable set to 0), meaning that line width and shading is NOT controlled by color.

3.3.4.2. The presentation graphics (line widths, line types, etc.) set in these CAD files must be modified to produce the desired readability of the final printed product. In general, drawings will be created using visual control that is manipulated by the layer; meaning color=’by layer’, line weight=’by layer’, line type=’by layer’.

3.3.4.3. In almost all cases, if these setting do not work, the items should be on separate layers.

3.3.5. Chapter 3, page 26, Line types/styles

3.3.5.1. The use of any line types/styles not in the templates available upon request must be approved by 502 CES.

3.3.6. Chapter 3, page 27/28, Plotting, Only the pen table(s) available upon request by 502 CES shall be used. (The named plot style – aecb and w.stb (required) is designed to be used with drawings requiring a named plot style. It has several settings – Black, Screen_40, Screen_50, Screen_60, Color, and Screen_50color, invisible).

3.3.7. Chapter 3, page 28-30, Text, all projects shall use Arial font. Upon approval: special fonts;

slanted text; and text styles may be used for business titles and logos in border sheets. If approved the font definition file must be supplied with the electronic files.

mailto:usaf%20jbsa.502-abw.mbx.502-ces-cad-

3.3.8. Chapter 3, page 28-30, Text Height

3.3.8.1. Varying size of text for like items shall be avoided. Applications are 1/2" – 1” for COVER TITLE type text.

3.3.8.2. 1/4” for Sheet Title text, i.e., FLOOR PLAN.

3.3.8.3. 3/16" for Sheet Item Titles typ. text, i.e., LEGEND, GENERAL NOTES, CURB DETAIL.

3.3.8.4. 1/8" for all new or demo work.

3.3.8.5. 3/32” for supportive text (i.e. contours, existing features).

3.3.9. Chapter 3, page 30, General Text Placement

3.3.9.1. General, project wide, non-sheet specific text may be placed in the model file, but shall only be placed at predominate text height and not duplicated at varying scales (i.e. room numbers, street names, coordinates, topographic points, etc. may be placed in the model file; all other text shall be placed in specific sheets).

3.3.9.2. All text (with the exception of 3.1.4.9.1) shall be placed in the Layout tab (Paper Space) of the Sheet file for which it pertains.

3.3.10. Chapter 3, page 31-32, Border Sheets

3.3.10.1. Only those border files available upon request by 502 CES shall be used. ANSI D (22x34) shall be used to facilitate direct 50% reduction to 11x17. The actual file adds an additional 2” (making it 22x36) which can be used for binding paper prints.

3.3.10.2. The border file available upon request from 502 CES is intended to be used with AutoCAD Sheet Set Manager (SSM), in which sheet text information is controlled through the SSM via the use of fields.

3.3.10.3. The Sheet Set definition is supplied with the template and shall not be modified. Modified meaning creation of additional field, etc., and does not apply to the required input of data.

3.3.10.4. A border that is intended to be used without utilizing the SSM will not be supplied. If the Contractor desires to not use the SSM, the Contractor will be required to modify the supplied templates for use with attributed blocks. Modification shall be approved via direct coordination with 502 CES prior to its use.

3.3.10.5. All border sheets must contain the information “Joint Base San Antonio, TX”.

3.3.11. Chapter 3, page 32, Issue Block

3.3.11.1. During Design, the revision number shall be represented with a “Circle & Number” and a description that provides a general statement of the revision.

3.3.11.2. Upon 100% Design and released for construction, all revision marks are erased and a single entry made; mark “1” in a “Circle” and note as “RELEASED FOR CONSTRUCTION.”

3.3.11.3. During construction, as modifications or differing conditions are found/made, the changes are reflected with a “Triangle & Number” and the description provides a general statement of the revision. The area of change is clouded and marked with a corresponding “Triangle & Number”.

3.3.11.4. At end of construction and completion of As-Built, all triangle marks and clouds are removed and replaced with a single statement above the “RELEASED FOR CONSTRUCTION” remark that reads “RECORD DRAWING AS-BUILT”.

3.3.11.5. If a sheet is altered to the degree that it must be re-issued, the new sheet shall contain the number “1” in a “Circle” with the “RELEASED FOR CONSTRUCTION” and original date mark with the next immediate mark being a number “1” with a “Triangle” and the remark “SHEET RE- ISSUED” or “SHEET REPLACED BY” and include the new sheet number.

3.3.11.6. All marks denoting a change shall include a modification, RFI, or change order number in the description.

3.3.12. Chapter 4, Page 44-53, Level/Layer Assignments

3.3.12.1. Only the layers defined in Appendix A shall be used.

3.3.12.2. The layer attributes for color, line type, line weight, and plot style must be modified to produce visually acceptable final prints.

3.3.12.3. ISO format layer names shall NOT be used unless directly coordinated through 502 CES.

3.3.13. Chapter 4, page 50, Reference Files

3.3.13.1. All reference files shall be on reference layers, i.e. X-XXXX-REFR.

3.3.13.2. All reference files shall be associated as a separate OVERLAY, meaning NO nested references.

3.3.13.3. All reference files shall be associated using a RELATIVE PATH.

3.3.13.4. All reference names shall match the reference file name in its entirety; ALIAS NAMES shall NOT be used.

3.3.13.5. All reference files shall be made in the Model Tab of the sheet drawing file, with the exception of the border sheet drawing. The Border sheet drawing shall be referenced in the Layout Tab (Paper Space) of the sheet drawing file. Border sheet drawing shall NOT be referenced in the Model Tab of a sheet drawing file.

3.3.13.6. All reference files shall be drawn at a scale of 1:1 (real size). Manipulation of the viewport in the Layout Tab (Paper Space) of the drawing sheet file shall be made to obtain the appropriate viewing/printing scale.

3.3.13.7. Changes to the drawing graphics shall be made to the external reference(s) (any changes made to the reference(s) will be automatically updated in the sheet file).

3.3.14. Chapter 5, Symbology

3.3.14.1. The A/E/C CAD standard, while supplying many symbols, does not meet current industry needs nor does it address the fundamental construction of block entities. The following guidelines shall be used in the creation of new blocks:

3.3.14.2. The Contractor shall fully document any custom made/used blocks in the files (meaning any block used that is not supplied by Joint Base San Antonio). Documentation shall include block name, description, and summary of use – i.e. how is it used and controlled. This documentation must be supplied with any and/or all drawing submittals as a “READ ME” file.

3.3.14.3. All symbol blocks shall be made with all entities on layer 0; color, line type, and line weight shall be set to BYLAYER. Line type scale for all entities will be set to 1.

3.3.14.4. Attributes shall follow the same guidelines as text, but shall also be placed on layer zero.

In some cases, it makes sense to have an attribute on a named layer – i.e., a survey control monument may have text on a Monumentation text layer so that it’s id may be turned off without effecting the block visibility. If this situation is used, the Contractor shall fully document the elements of a block that are not constructed on layer 0 and have this documentation of the block APPROVED prior to use.

3.3.14.5. Block Symbols must be constructed with the insertion point set to 0, 0, 0. (The base point of all drawings shall be 0, 0). Example, if the symbol is a manhole, the insertion point would be the center of the manhole, which would be at 0, 0, 0.

3.3.14.6. Block names shall follow layer naming conventions- i.e. a surveyed Sanitary Sewer manhole would be V-SSWR-MNHL. Contact by email: usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil. for any question or concerns in regards to A/E/C CAD Standard, CAD Drafting Standard, and/or this document.

--END OF SECTION 01 35 13.20 00--

Attachment 6_ Appendix E_01 35 13.20 00 Special Project Procedures - CAD