Appendix D - HC1028R0067.pdf

Page 1 of 13 Version Date: 22 December 2010

DISA Computing Services Division (CSD) Facilities Engineering Team (CD521)

Drawing Configuration Management (CM) Specification

Purpose: This specification, as part of the DISA Computing Services Facilities Standards (CSI 360-95- 3), is to define the requirements of a consistent, sustainable drawing management system for use in the CD521 Facilities Engineering office, and as a part of all contracts, projects, and programs that will use, create, modify, or supersede record drawings.

Table of Contents:

Scope

Applicability

Definitions

References

General Requirements

Filespaces for Drawing Configuration Management

Drawing Naming Convention

Record Drawings

Title Block

As-Built Drawing Title Block Requirements

Layers

As-Built Layer Requirements

Change Control

Drawing Composition

Line, Object, and Entity Properties

Model and Layout (Paper) Space Usage

External References (XREFs)

Drawing File Transmittal

Legacy Drawings

Boilerplate for Project SOWs/PWSs

Appendix 1: As-Built Drawing Quality Assurance (QA) Checklist

Page 2 of 13 Version Date: 22 December 2010

All facility and facilities infrastructure systems visual representations (layouts, maps, one-lines, block diagrams, and similar) are covered by this specification. Computer room layout drawings (showing the location of IT equipment) maintained in the Aperture/ADM systems are not in the scope of this specification.

Scope

Except as otherwise noted in this specification, drawings shall follow guidance in mandatory reference ERDC/ITL TR-09-2 A/E/C CAD Standard (current release) with respect to electronic file naming conventions, layer assignments and naming conventions, reference files (XREFs), and standard symbology.

This specification is mandatory guidance for all projects that modify CD521-managed facilities, whether the work is planned & executed by CD521 personnel or not. Work conducted at CD521-managed facilities is required to follow DISA Computing Services Facilities Standards.

Applicability

A drawing, for the purposes of this specification, is an AutoCAD .dwg vector-based electronic file representing an object or system through the use of lines and other geometric constructions. A drawing is an accurate representation of an actual item that can be used for design, construction, and to convey information about the represented object. Drawings in other electronic file formats may exist, providing legacy (historical) information only.

Definitions

A record drawing, for the purposes of this specification, is a (final) current configuration of a building or system. The record drawing is the basis for all planning or working drawings. Only certain drawings are considered record drawings; this is the highest level document classification and has the strictest administrative controls imposed to ensure correctness. Record drawings shall be in AutoCAD format only.

A supporting drawing, for the purposes of this specification, is a (final) current drawing that shows additional details about a building or system not shown in the record drawings for a particular building or system. All (final) current drawings relating to a building or system that are not record drawings are classified as supporting drawings. Supporting drawings are generally necessary to provide complete, drill-down, detailed information regarding a construction, installation, or system. Not all types of systems or buildings will have the same level of supporting drawing documentation; some may not have any.

Supporting drawings may be in AutoCad or PDF (scanned) formats. Supporting drawings in other file formats (TIF, BMP, et cetera) shall be converted to PDF.

Planning drawings and working drawings, for the purposes of this specification, are copies of record or supporting drawings used for the development of future work. They are based on a specific revision of a record or supporting drawing. Planning and working drawings are maintained in different locations than the record and supporting drawings to avoid confusion regarding their status, and require ownership by a project engineer or project manager. Planning and working drawings allow the creation of red-line and as-built drawings.

http://www.wbdg.org/ccb/browse_org.php?o=65�

Page 3 of 13 Version Date: 22 December 2010

Red-line drawings, for the purposes of this specification, are intermediate drawings that notate changes or corrections to planning or working drawings prior to the generation of as-built drawings. Their existence reflects that work will not be completed exactly as planned and records those changes during the progression of work so that information is not lost. Red-line drawings are informal and are not managed by this specification.

As-built drawings, for the purposes of this specification, are those that are made during a project, recording the differences between the original design and the completed project. As-built drawings are the change control documentation that allows modification of record drawings and supporting drawings during the close-out phase of a project. As-built drawings are typically formal electronic drawings that are created and submitted by a contractor as part of the project. As-built drawings require ownership by a project engineer or project manager.

Revision is the version of a particular record or supporting drawing; revisions are created by the change control system and ensure that only the (final) current version of a drawing is used for creating planning and working drawings. Older revisions of a managed drawing are maintained in change control locations to allow diagnosis, troubleshooting, and to provide other historical functions.

Superseded means any managed drawing that is not the (final) current version. Older revisions of documents are marked as superseded to ensure that they are not used instead of more current versions.

Ownership means that a drawing is attached to a project where changes are being made to a record or supporting drawing. A project engineer or project manager (the project lead) has ownership of the planning, working, and as-built drawings for that project. Ownership implies responsibility for the correct management of drawings and processes in the scope of this specification. Ownership requires the project lead to follow all guidance in this mandatory specification. Ownership responsibilities are not limited to CD521 personnel; other organizations that plan and execute work in CD521-managed facilities are required to take ownership of their projects.

Except as otherwise noted in this specification , drawings shall follow guidance in mandatory reference

References

ERDC/ITL TR-09-2 A/E/C CAD Standard (current release) with respect to electronic file naming conventions, layer assignments and naming conventions, reference files (XREFs), and standard symbology.

All drawings in the purview of this specification shall be electronic. As-built drawings shall be submitted in electronic format compatible with the current version of AutoCAD. Paper-based drawings are being eliminated except for prints of existing electronic drawings and concurrently submitted paper review sets of electronic planning and working drawings. Under no circumstances shall paper-based drawings be allowable for record, supporting, or as-built drawings.

General Requirements

Drawings shall be saved in paper (layout) space such that when they are opened the view is as the drawing will print, including the title block.

Page 4 of 13 Version Date: 22 December 2010

All drawings shall be created at full scale (1:1) in model space. Plotting to scale shall be based on the standard DISA title block.

Record and supporting drawings shall be maintained in site-based file folders on the Denver HQ servers.

No other drawings or other documents shall be maintained in this filespace. The path for record and supporting drawings is:

Filespaces for Drawing Configuration Management

S:\facility\Sites\[sitename]\ Drawings

Record and supporting drawings shall not be maintained in other folders, to include project folders.

Planning, working, red-line, and as-built drawings shall be maintained in site-based project folders on the Denver HQ servers. The approved paths for planning, working, red-line, and as-built drawings is:

S:\facility\Sites\[sitename]\ Project Files or

S:\facility\Raised Floor Management\[sitename]

Page 5 of 13 Version Date: 22 December 2010

Individual drawings shall be named in accordance with the model file naming convention (figure 2-4) in mandatory reference

Drawing Naming Convention

ERDC/ITL TR-09-2 A/E/C CAD Standard (current release), which combines the sheet number with the sheet name. This convention follows the format:

where references “Table 2-1” and “Table 2-2” are from mandatory reference ERDC/ITL TR-09-2 A/E/C CAD Standard (current release). All record and supporting drawings shall be assigned sheet numbers to be standardized to the extent possible.

Sample discipline designators are E- (Electrical), S- (Structural), M- (Mechanical), G- (General), and A- (Architectural). Sample Model File Types (which may be specific to each discipline) include DT (Detail), FP (Floor Plan), EL (Elevation), KP (Key Plan), and DG (Diagram). Not all Model File Names are allowed in all disciplines. See Tables 2-1 and 2-2 for further details.

One-line and block diagrams for the Electrical and Mechanical disciplines shall use nomenclature

E-DGxxxx-Sheet Name.dwg and M-DGxxxx-Sheet Name.dwg.

Sheet G-KP0001 is reserved for an index of drawings for all sites/facilities. The filename for the drawing index for each site/facility shall be G-KP0001 – Index of Drawings.dwg. An example of a (legacy) drawing index is shown below:

Naming of record and supporting drawings in alternative manners is not authorized. Legacy drawing names such as “ACAD_MONT857_1st_Floor.dwg” shall be converted to the standard drawing name convention format where the drawing is to become a record or supporting drawing.

http://www.wbdg.org/ccb/browse_org.php?o=65�

Page 6 of 13 Version Date: 22 December 2010

There are no mandatory naming conventions for planning and working drawings. However, as the result of a planning or working drawing will typically be an as-built drawing, and as as-built drawings will be incorporated into or replace existing record and supporting drawings, project leads are strongly encouraged to follow a naming convention such as:

[sheetname]-[sitename]-[projectname].dwg

For example, M-DT15-Philadelphia-Bell Repair.dwg could be the filename for a working drawing to eventually update supporting drawing M-DT0015.dwg.

Record drawings are the primary top-level drawings of the facility or major systems that are used most frequently in the transmission of concepts and information regarding DISA facilities. A very limited subset of (final) current drawings shall be designated as “record” for the purposes of this specification.

Record Drawings

Drawings with the following content shall be designated as record drawings for each site:

The Drawing Index for the site. The filename for this sheet shall be G-KP0001 – Index of Drawings.dwg.

The overall floorplan (facility layout) for the site. Each individual building and floor at a site shall have its own sheet. The floorplan shall have layers showing the walls, raised floor areas, room numbers. Systems furniture, IT equipment, security systems, and infrastructure equipment shall not be shown on these record drawing sheets. The filenames for these sheets shall follow the format A-FPxxxx-[Building][buildingnumber]-[Floor][floornumber]-Master Floorplan.dwg, where italicized information shall be included only if there are multiple buildings/floors located at the site. Therefore, example filenames could include:

A-FP0001-Master Floorplan.dwg (single facility, single floor).

A-FP0004-Building550-Master Floorplan.dwg (multiple facilities, single floor).

A-FP0006- Floor3-Master Floorplan.dwg (single facility, multiple floors).

A-FP0012-Building375-Floor3-Master Floorplan.dwg (multiple facilities, multiple floors).

The top-level electrical one-line diagram for the site. These drawings show the flow of electricity from commercial and locally generated sources, all switchgear and major transformers, uninterruptible power supply systems, essential distribution to the MCC bucket level, and the distribution to the PDU level for critical busses. Individual panels, schedules, lighting, and non-critical non-essential buss distribution are not included in these record drawings. The filenames for these sheets shall follow the format E-DGxxxx-[Building][buildingnumber]-Sheet Name where italicized information shall be included only if there are multiple buildings located at the site.

The facility block diagrams for critical mechanical infrastructure systems at the site. These drawings show how existing infrastructure systems are installed and function to support the critical loads. Example systems to be diagrammed in these drawings are the chilled water generation and distribution system, condenser water distribution system, and fuel system storage & distribution systems. The filenames for these sheets shall follow the format M-DGxxxx-

Page 7 of 13 Version Date: 22 December 2010

[Building][buildingnumber]-Sheet Name where italicized information shall be included only if there are multiple buildings located at the site.

All other (final) current drawings shall be designated as supporting drawings.

The general DISA Computing Services title block sheet shall be a layout space (also known as paper space) template (.dwt) sized for ANSI D (22”x34”) in landscape orientation. Plots made of record and supporting drawings shall be made from layout (paper) space showing the complete title block.

Title Block

Information on the title block sheet attached to each different drawing shall be specific to that drawing, and shall include revision (change control) number information. The Drawing Phase block on the title block shall indicate the version status of all documents: Only a single (current) revision of any record or supporting drawing shall be marked as “CURRENT” at any time; other versions shall be marked as “SUPERSEDED” and moved to the appropriate legacy filespace when the updated document is published.

The Revision section of the title block shall contain the current revision number, a brief summary of the change(s) or project causing the revision, the revision effective date, the owner of the project causing the revision, and the initials of the individual completing the revision.

Title blocks for submitted

As-Built Drawing Title Block Requirements as-built drawings shall be drawn with the lower-left-hand corner point inserted at a Cartesian coordinate location of (0, 0, 0). All title blocks within submitted as-built drawings shall contain the following information:

Original Issue Date – this date shall not change once the drawing has been issued and shall remain the same on every drawing throughout the drawing set.

Sheet Number – a unique identifier which refers to the discipline and number of the drawing in the set. Do not assign numbers longer than 8 digits.

Title – description of drawing and location information. Location information shall include building, floor and room numbers as applicable.

Revision History – as applicable to the as-built drawing (not the source record or supporting drawing).

Drawing Phase – drawings submitted as as‐builts shall be clearly marked as “AS-BUILT” (not as “CURRENT” or “SUPERSEDED”, which are reserved for record and supporting drawings).

Architect, Engineer or Consultant – the company/organization and individual responsible for producing the drawings shall be clearly identified.

Drawing Scale(s) – representing the intended plot scale of the drawing with the title block. Sheets containing more than one scale shall state “as noted” in the space on the title block where the scale is usually located, and each scale shall be included as it applies to each drawing, section or detail.

North Arrow – as applicable.

Layers

Page 8 of 13 Version Date: 22 December 2010

In order to effectively use and manipulate model and layout (paper) information in each drawing, all layers and their uses shall be standardized by name and use throughout the drawing system. The layers used in all DISA drawings shall comply with the recommendations of the AIA CAD Layer Guidelines

(AIA 2007).

A complete list of available layers and their properties is included in Appendix A (Model File Level/Layer Assignment Tables) and Appendix B (Sheet File Level/Layer Assignment Tables) of ERDC/ITL TR-09-2 A/E/C CAD Standard (current release). Drawings maintained by or submitted to DISA shall use only AIA-recommended layer names from these two Appendices.

Use the minimum number of layers necessary to adequately separate entities in each drawing. The number of layers contained in each drawing will vary depending on the scope and complexity; however drawings shall not contain extraneous or redundant layers.

Record and supporting drawing files maintained by DISA shall not contain any frozen layers. Frozen layers may only be used in planning and working drawings.

As-built drawing

As-Built Layer Requirements files submitted to DISA shall not contain any frozen layers. Unused entities on frozen layers shall be erased, the empty layers purged, and all layers thawed.

Purge each drawing of unused and/or unnecessary layers prior to submittal to DISA. The drawing file shall contain only those layers necessary for displaying and plotting the information and drawing entities contained within each drawing.

Record and supporting drawings shall be given read-only attributes to protect the original files. Use of record/supporting drawings for planning/working drawings shall be accomplished by saving the file(s) under their planning/working drawing filename(s) in the appropriate filespace(s).

Change Control

Change control of record and supporting documents shall be conducted by file management processes.

Superseded drawings are never deleted; they are instead moved to archive spaces in the change control filespace. Specific additional documentation is not planned. Maintenance of the change control records is the responsibility of the project lead having ownership of a project that makes changes in a record or supporting drawing. Information detailing the most current change(s) to the drawing are found in the Revision section of the title block for the drawing.

The primary indication of the (final) current record document is the Drawing Phase indicator in the title block: Only a single (current) revision of any record or supporting drawing shall be marked as “CURRENT” at any time; other versions shall be marked as “SUPERSEDED” and moved to the appropriate legacy filespace when the updated document is published.

The secondary indication of the status of a record or supporting drawing shall be its physical location in the filespace, as shown in the CD521 Drawing Configuration Management (CM) Hierarchy.

Page 9 of 13 Version Date: 22 December 2010

The revision number of a newly created or updated (final) current document shall be the next ordinal whole number, starting with null (0). For example, a revision to existing revision 5 of a drawing would be assigned revision number 6, and a drawing for a new facility or system with no revision history would be assigned revision number 0.

Drawing files shall contain only one drawing (model) and one title block per file.

Drawing Composition

Drawing files shall not contain more than one drawing sheet per file, either by multiple drawings in model space or spread out across several layouts. While multiple drawings and layouts may facilitate the production of construction documents, it impedes the archival and configuration management processes, and creates content discrepancies.

As-built drawing files containing multiple drawing sheets shall be broken down into single sheets prior to delivery to DISA.

All drawing files shall be purged of empty, unused, or non‐essential drawing data prior to submittal. This includes the removal of all unused layers, linetype, blocks, fonts, dimension styles, and other entities.

Unused objects and entities contained in the drawing must directly apply to the specific purpose of the drawing with the exception of the title block.

Drawing files shall not contain multiple overlaid lines or lines with multiple segments unless the overlaid lines or adjacent line segments are assigned to different layers. Multiple overlaid lines or blocks can be removed from the drawing by using the “OVERKILL” command.

Drawings shall use symbology in mandatory reference

Line, Object, and Entity Properties

ERDC/ITL TR-09-2 A/E/C CAD Standard (current release). Where necessary symbols are not present in the reference document a DISA-standard symbol shall be created. Future versions of this specification shall include any DISA-specific symbols developed for this purpose.

Entity colors shall be defined by layer, not entity.

Blocks shall be defined/created on layer null (0).

All attributes shall be defined on layer null (0).

All lines, objects, blocks and entities must be drawn where the Z‐axis is null (0), meaning there is no elevation to the elements in the drawing and the drawing is truly 2‐dimensional.

Drawings created using non‐standard AutoCAD™ fonts, linetypes and hatch patterns can result in content discrepancies in the delivered drawing set. The following guidelines will ensure the integrity of the drawing set, and minimize potential problems:

Only native AutoCAD fonts, linetypes, hatch patterns, and the approved CAD symbology are acceptable.

Page 10 of 13 Version Date: 22 December 2010

Custom fonts, linetypes and hatch patterns including those provided by 3rd party software, are not acceptable.

Postscript fonts shall not be used.

Place title blocks, schedules and general notes at full‐scale (1:1) in layout (paper) space.

Model and Layout (Paper) Space Usage

Do not place or draw model‐related blocks, tags and objects in layout (paper) space.

Draw all model space objects at full (1:1) scale.

Scale objects as necessary using layout (paper) space viewports; zoom viewports to the appropriate scale.

External references (XREF’s) are described as a reference to another, external file — one outside the current drawing — that is inserted into a drawing as a block and that may be manipulated according to the type of referenced file. Objects brought into a drawing as an outside source may include (but are not limited to) AutoCAD drawings (.dwg), images (.JPG, .GIF, .PNG, .BMP, et cetera) or other files (.pdf, .dwf, .dgn, et cetera). XREFs contained within drawings may be helpful, but when the drawing and/or XREF locations are moved around discrepancies are likely to occur within the drawing set. The following requirements will ensure the integrity of the drawing set and minimize potential problems.

External References (XREFs)

Externally-referenced blocks shall be exploded and the resulting objects placed onto the appropriate layer.

All drawings containing other drawings as an XREF shall bind the external referenced drawing into the main drawing. This should be done using the “Insert” bind type. (All drawings shall be stand-alone in final, published configuration.)

All layers contained in XREFs inserted as blocks shall conform to the guidance in this specification.

As-built drawings shall not contain any XREFs. External references (excluding .dwg drawings) shall be inserted into drawings as blocks rather than as XREFs.

File translation from non‐AutoCAD systems resulting in wall blocks within AutoCAD are unacceptable.

Planning, working, and as-built drawings used for project review shall require both a hard copy (ANSI B or larger) and an electronic copy of the complete drawing set for the project. The content of electronic as-built drawings shall match the delivered original hard copy set as closely as possible, if not exactly (same revision).

Drawing File Transmittal

To ensure drawings adhere to the guidelines presented in this specification, the As-Built Drawing Quality Assurance (QA) Checklist (see Appendix 1) shall be completed and submitted with all drawing packages submitted to CD521, including all design review packages (35%, 90%, et cetera).

Page 11 of 13 Version Date: 22 December 2010

Drawing packages not in full compliance with this specification are not acceptable and shall result in re-work at no additional cost to the Government. Payment for services shall not be rendered until all specification requirements are complied with.

All physical objects shown in plan, elevation, or detail sections shall be drawn in actual size and then scaled appropriately for plotting. To avoid scaling problems or drawing distortions nominal sizes shall not be used.

Include all AutoCAD .PC2, .PCP or .CTB plot configuration files used to make the final prints to ensure CD521’s ability to make exact printed re‐creations of drawings from the project.

CD521 recognizes that vector-based electronic files compatible with the current drawing software may not exist; in some cases only paper or raster-based electronic files may be available. This section defines the requirements for maintenance of this legacy information.

Legacy Drawings

Legacy drawings, just as superseded drawings, are never deleted. Any versions of record or supporting drawings shall be maintained in the “Legacy PDF Drawings” subfolder as shown in the CD521 Drawing Configuration Management (CM) Hierarchy. Versions of other drawings shall be archived in the “Archived Drawings” subfolder with an attachment describing the drawings’ original purpose(s). No format is specified for the attachment providing supplementary information.

Legacy paper-based drawings shall be scanned and named based on the content of the drawings. Scans shall be accomplished at 600dpi in grayscale into ISO 32000-compatible Portable Document Format (PDF) format. Resulting documents shall be cropped to reasonable margins with no loss of resolution as necessary.

A legacy drawing set may have its own index of drawings; this index is not required to match the (final) current record drawing index. If an index does not exist for the set, one shall be created. The index may be in standard .dwg format.

Legacy drawings provided in Tagged Image File Format (TIFF) or other raster-based electronic format shall be converted to PDF as noted above, and renamed as appropriate.

Boilerplate for Project SOWs/PWSs The following boilerplate text shall be placed into the General Requirements section of each project’s Statement of Work (SOW) or Performance Work Statement (PWS). The presented information guides the contractor (vendor, architect/engineer, et cetera) to the current version of this specification for detailed information. The boilerplate will address the high-level requirements of this specification:

Upon substantial completion of the project and as a condition of project closeout, the Contractor shall provide an as-built drawing package meeting the following requirements. Drawing packages not in full compliance with this requirement are not acceptable and shall result in re-work at no additional cost to the Government. Payment for services shall not be rendered until all requirements are complied with and http://en.wikipedia.org/wiki/Portable_Document_Format� http://en.wikipedia.org/wiki/Portable_Document_Format� http://en.wikipedia.org/wiki/Portable_Document_Format�

Page 12 of 13 Version Date: 22 December 2010 accepted, by signature on the As-Built Drawing Quality Assurance (QA) Checklist, by the CD521 project lead.

Design review drawing packages shall meet the same requirements as as-built drawing packages, but do not require signature on the As-Built Drawing Quality Assurance (QA) Checklist by the CD521 project lead for acceptance.

As-built drawings shall meet all requirements of the current DISA Record Drawing Configuration Management Specification (section 01 78 39 (Project Record Document) of CSI 360-95-3, DISA Computing Services Facilities Standards). As-built drawing transmittal shall be by hand or by tracked shipping organization with guaranteed delivery window (USPS, UPS, Federal Express, or similar).

Formal transmittals shall include both electronic and hard-copy simultaneously; separate deliveries are not acceptable. Two (2) sets of hardcopy drawings in not less than ANSI B size are required for all formal transmittals. Transmittals shall be made simultaneously to the CD521 project lead and the DISA Facility Manager at the following offices:

CD521 Project Lead DISA Facility Manager DISA Computing Services

Mr. John Public, CD521 Facilities Engineering 340 Iron View Circle

Fort Powell, MT 59520 email: John.Public.ctr@csd.disa.mil

989.555.1212

DISA San Bernadino ATTN: Ms. Jean Smith, Facility Manager

1200 Dewy Nectar Pike, Bldg 550 San Bernadino, CA 92401 email: Jean.Smith@csd.disa.mil 415.555.1212

**End of Line** http://tiny.cc/StdsFolder775� http://tiny.cc/StdsFolder775� mailto:John.Public.ctr@csd.disa.mil� mailto:Jean.Smith@csd.disa.mil�

Page 13 of 13 Version Date: 22 December 2010

AutoCAD drawings delivered to DISA Computing Services at project closeout shall be accompanied by submission of this CAD Quality Assurance (QA) Checklist. A signed checklist indicates to DISA Computing Services that the standards, specifications, and guidelines were read, understood and complied with.

Appendix 1: As-Built Drawing Quality Assurance (QA) Checklist

FILE FORMAT AND SETUP

□ Electronic File Format

□ Scale, Units, & Tolerances

□ Fonts and Text Styles

□ Blocks

□ Title Blocks

□ Policy on Model Space and Layout (Paper) Space

□ Policy on External Reference Files (XREFs)

LAYERING

□ Standard Layer List

□ Layer Name Formatting

□ General Rules about Naming and Uses

□ Layer Attributes (Colors, Pens, Linetypes)

FILE NAME CONVENTIONS

□ Building and Floor Identification Codes

□ Discipline Identification Codes

□ Drawing Type Codes

□ Drawing Numbers

POLICY ON SCANNED FILE TRANSLATION

□ Scan at 600 dpi

□ Files must be uncompressed

Signature, Vendor Representative _______________________________________

Phone Number ________________________ Date ________________________

Signature, DISA CD521 Project Owner __________________________________