Attachment_J_Electronic_Data_Standards_(EDS)_Rev._4.1_(January_25 _2006).pdf

Pentagon Renovation & Construction Program Electronic Data Standards

The Pentagon

Washington, DC

Revision 4.1

January 25, 2006

Volume 1 of 1

Government POC:

Sandra Dutson

(703) 693-7688

Contract No.: TBD

Delivery Order No.:TBD Amendment No.: N/A Modification No.: N/A

Prepared by:

Information Resource Center (IRC) IPT 110 Boundary Channel Drive

Arlington, VA

IRC IPT POC:

Michael Jackson

(703) 693-7192

*** FOR OFFICIAL USE ONLY ***

TABLE OF CONTENTS

Table of Contents

1 Introduction

1.1 General Information

1.1.1 Credits

1.1.2 Purpose

1.1.3 Pentagon Renovation Program Web Site

1.1.4 Scope

1.1.5 Responsibility

1.1.6 Organization of PRPEDS

1.1.7 Acronyms

1.1.8 General Definitions

1.2 Executive Summary

1.2.1 Background

1.2.2 File Formats

1.2.3 CADD Standards

1.2.4 Text Document Standards

1.2.5 CPM Construction Schedule Standards

2 CADD Standards

2.1 General CADD Information

2.1.1 Purpose

2.1.2 CADD Definitions

2.1.3 CADD Standards

2.1.4 History of the CADD Standards

2.2 Coordinate System and Building Orientation

2.2.1 Maryland State Coordinate System

2.2.2 Geographical and Non-Geographical Drawings

2.2.3 Global Origin

2.2.4 PRP Monument Point

2.2.5 Pentagon Coordinate Points

2.2.5.1 SURVEY and DESIGN Coordinate Points

2.2.5 Pentagon Floor Elevations

2.2.6 MicroStation Design File Setting

2.3 CADD File Organization

2.3.1 Project Folder Structure

2.3.2 3D Design File Organization

PENTAGON RENOVATION & CONSTRUCTION PROGRAM SEPTEMBER 25, 2006

ELECTRONIC DATA STANDARDS i

2.3.3 3D Model Files

2.3.4 Extraction Files

2.3.5 Reference Files

2.3.6 Contract Sheet Files

2.4 Border File

2.5 CADD File Identification

2.5.1 CADD File Naming Syntax

2.5.1.1 Project Identifier

2.5.1.2 Discipline Designator

2.5.1.3 Discipline Modifier

2.5.1.4 Sheet Number

2.5.1.5 New Sheet Insert Identifier

2.5.1.6 File Name Delimiter

2.5.1.7 File Extension

2.5.1.8 3Dmodel File Name

2.5.1.9 Extraction File Name

2.5.1.10 Tenant Extraction File Name

2.5.1.11 Reference File Name

2.5.1.12 Tenant Reference File Name

2.5.1.13 ‘Contract Sheet’ File Name

2.5.1.14 Tenant ‘Contract Sheet’ File Name

2.5.1.15 Cell Library Name

2.5.1.16 Cell File Name

2.5.1.17 3D Model Family and Parts Name

2.5.1.18 View Group Name …………………………………………………………………. 18

2.5.2 Cross Reference identification between Contract Sheet Files

2.6 CADD File Settings

2.6.1 Graphic Scales ............................................................................... Error! Bookmark not defined.

2.6.2 Views

2.6.3 Default View Settings

2.6.4 Level Symbology

2.7 Support Files

2.7.1 Seed Files

2.7.2 Color Table

2.7.3 Cell Libraries and Cells

2.8 Level Definitions

2.8.1 Building Information

2.8.2 Drawing Information

2.8.3 Level Naming Conventions

2.8.4 Level Name Syntax

2.8.5 Level Assignment Tables

ELECTRONIC DATA STANDARDS ii

2.9 Dimensioning

2.9.1 Dimension Setting

2.9.2 Dimensioning Styles

2.9.3 Dimensioning in Imperial

2.10 Text

2.10.1 Text Justification

2.10.2 Text Fonts

2.10.3 Drawing Title Block Text

2.11 Element Characteristics

2.11.1 Line Weight

2.11.2 Pen Widths

2.11.3 Line Styles

2.12 Border File

2.13 Plotting

2.13.1 Plotter Drivers

2.13.2 Pen Tables

2.14 Requirements for Electronic Delivery

2.14.1 CADD Deliverables

2.14.2 Delivery Media Preparations

2.14.3 Labeling Delivery Media

2.14.4 Delivery Media Information

2.14.5 Delivery Media

2.15 CADD Standards Compliance

2.15.1 A/E/C Quality Control Plan

2.15.2 CADD Software

3 Text Document Standards

3.1 Purpose

3.2 Document Cover Standards

3.2.1 Report Covers

3.2.2 Specifications Covers and Report Flysheets

3.3 Documents - Text Based

3.3.1 Presentation Guidelines

3.3.1.1 Report Format

3.3.1.2 Specifications Format

ELECTRONIC DATA STANDARDS iii

3.3.2 Electronic Formats

3.3.2.1 Source Format

3.3.2.2 View and Print Format

3.3.3 Catalog

3.4 Documents - Spreadsheet

3.4.1 Presentation Guidelines

3.4.2 Electronic Formats

3.4.2.2 Source Format

3.4.2.3 View and Print Format

3.4.3 Catalog

3.5 Documents - Vector Graphics

3.5.1 Presentation Guidelines

3.5.2 Electronic Formats

3.5.2.1 Source Format

3.5.2.2 Web Viewing Format

3.5.2.3 Catalog

3.6 Documents – Raster Graphics

3.6.1 Presentation Guidelines

3.6.2 Electronic Formats

3.6.2.1 Source Format

3.6.3 Catalog

3.7 Documents - Presentation

3.7.1 Presentation Guidelines

3.7.2 Electronic Formats

3.7.2.1 Source Format

3.7.3 Catalog

3.8 Reports – Project Management

3.8.1 Presentation Guidelines

3.8.1.1 Schedule Presentation Guidelines

3.8.2 Electronic Formats

3.8.2.1 Source Formats

3.8.3 Catalog

3.9 Documents - Compound

3.9.1 Presentation Guidelines

3.9.2 Electronic Formats

3.9.2.1 Source Format

3.9.2.2 View and Print Format

3.9.3 Catalog

4 CPM Construction Schedule Standards

ELECTRONIC DATA STANDARDS iv

4.1 Presentation Guidelines

4.1.1 Electronic Formats

4.1.1.1 Source Format

4.1.2 Catalog

5 Appendix A – Discipline Designators and Discipline Modifiers

5.1 Common Discipline Modifiers

5.2 Discipline Designators and Discipline Modifiers

6 Appendix B - CADD Level Assignments and Descriptions

B.1. General Levels on Sheet File For All Disciplines

B.2 Levels on Design Model and Reference Files by Each Discipline

B.2.1 Architecture (A), (B)

7 Exhibits

Exhibit A.1 - Directory Structure

Exhibit A.3 - Title Block

Exhibit A.4 - Standard Imperial Sheet Sizes

Exhibit A.5 - Typical Imperial Drawing Scales

Exhibit A.6 - Associated Pen Widths

Exhibit A.7 - CADD File Catalog

Exhibit A.8 - CADD Compliance Checklist...................................Error! Bookmark not defined.

8 Appendix D – PRPEDS Revision Details

ELECTRONIC DATA STANDARDS v

1 - INTRODUCTION

1 Introduction

PENTAGON RENOVATION & CONSTRUCTION PROGRAM JANUARY 25, 2006

ELECTRONIC DATA STANDARDS 1

1.1 General Information

1.1.1 Credits

This standard was originally derived from the Tri-Service CADD Standards (produced by the Tri-Services CADD/GIS Technology Center located in Vicksburg, Mississippi) and was customized by the PENTAGON RENOVATION PROGRAM to meet the requirements of the Pentagon Renovation. Subsequently, at the request of the PENTAGON RENOVATION PROGRAM, the standard has been updated to incorporate, where appropriate, the latest National CAD Standard (version 2) produced by the 'National Institute of Building Sciences'.

1.1.2 Purpose

The purpose of the EDS is to provide criteria and guidelines for all electronic data produced by All A/E/C Contractors and their Subcontractors as well as other A/E/C contractors and their subcontractors. These standards are designed to aid managers, architects, engineers, and construction contractors in the production of homogeneous, accurate and professional CADD and Text Documents.

The EDS will be updated by the A/E/C based on evolving project requirements and technology over the life of the Wedges 2-5 renovation and will be distributed to PenRen for review as changes are made.

It is the policy of the PenRen Office that all CADD, text documents, and all other PRP contract deliverables covered in this standard are delivered in the appropriate electronic format(s) as described in these standards.

1.1.3 Pentagon Renovation Program Web Site

The standards and support files indicated in this standard are available at the following URL www.renovation.pentagon.mil.

1.1.4 Scope

These standards shall apply to all work performed by All A/E/C Contractors and their Subcontractors, other A/E/C contractors and their subcontractors under contract with the PenRen Office.

If any portion of this document is such that as instructed, a required result cannot be achieved due to technical limitations of related hardware and/or software applications then it should be brought to the attention of the PenRen Office immediately for review and consideration.

These standards may be applied to any other work so designated by the Government.

ELECTRONIC DATA STANDARDS 2

1.1.5 Responsibility

The EDS IPT, Information Resource Center, Government project managers, Government Contract Officers, A/E/C contractors, Sub-Contractors, Editors, Document Authors, CADD specialist, and designers involved with the PRP are responsible for ensuring that electronic deliverables conform to these standards.

1.1.6 Organization of PRPEDS

Section 1 – Introduction contains general information about these standards.

Section 2 – CADD Standards covers specific standards for architectural, engineering, and some presentation drawings. This section establishes drawing presentation guidelines and specific criteria for CADD deliverables.

Section 3 – Text Document Standards covers specific standards for Text-intensive documents.

Such document deliverables include studies, reports, specifications, etc.

Section 4 – Project Controls Standards covers specific standards for project schedules.

Appendices - Contains exhibits, graphic illustrations, charts, and tables, etc.

1.1.7 Acronyms

• A/E/C - Architecture, Engineering, and Construction

• AIA - American Institute of Architects

• CADD-Computer Aided Design and Drafting

• CPM – Critical Path Method

• DGN - MicroStation V8 Triforma 3D Design File

• DoD - Department of Defense

• EDS IPT – Electronic Data Standards Integrated Product Team

• MSAE - Management Support Architect/Engineer

• MSCS - Maryland State Coordinate System

• PRP- Pentagon Renovation Program

• ANSI - American National Standards Institute

ELECTRONIC DATA STANDARDS 3

1.1.8 General Definitions

• A/E Design Contractor - Architectural/Engineering firm who is responsible for the production of the contract documents for a specific Pentagon Renovation Program construction project.

• Amendment - Written or graphic documents that are issued during the solicitation

(construction bidding) period which modify or interpret the bidding documents, including drawings and design specifications. Amendments may include additions, deletions, clarifications, or corrections. Amendments involving drawings may be executed by written description with or without reissue of modified/new drawings. Amendments become part of the contract documents when the contract is executed.

• Construction Contractor - A group that enters into a mutually binding relationship with the Government for the construction, alteration or repair of buildings, structures or other real property in support of the PRP. This term includes the general contractors and sub-contractors.

• Delivery Order - Government issued sub-contract for design services.

• Management Support Architect/Engineer - The Architectural and Engineering firm who will provide overall project management to plan, organize, assist, and coordinate the work to be performed in support of the PRP.

• Modification - The officially approved set of documents issued by the Government to modify the contract.

• Sub-Contractor - Any person or group under contract to a primary design or a construction contractor.

1.2 Executive Summary

1.2.1 Background

The Pentagon Renovation Program (PRP) is a comprehensive effort to renovate the Pentagon and its support facilities and infrastructure throughout the Pentagon Reservation. Work on the PRP will be completed in many phases, and will involve several different government groups and contractors. Each phase of the renovation will bring about the creation of an enormous amount and variety of electronic and hard copy documents. These documents are related to the design, construction, and operation of the renovated Pentagon. The type of documents range from studies and reports to 3D animations to databases. These documents and the information that they contain will be used to populate various databases and decision support systems (databases). Upon completion of the PRP, a subset of these documents will be given to the building owners to populate their Facilities Data Management System (FDMS). In order to maximize the usefulness of such information management systems, as many documents as

ELECTRONIC DATA STANDARDS 4

possible must be electronic, accurate, and standardized.

The Pentagon Renovation Program Electronic Data Standards is an important part of meeting these three goals. The PRPEDS are a contractually binding part of all PRP contracts involving the delivery of electronic documents. Throughout the renovation, many groups have played a part in the ongoing effort to update the electronic standards. For the most part, updates to the electronic standards occur as the demands for information by PRP decision-makers change or increase. The PRPEDS currently cover three major types of electronic documents: CADD, Text Documents, and CPM Schedules. A summary of standards governing these document types is given below.

1.2.2 File Formats

The PRPEDS standards require that all CADD, Text Document, and Schedule deliverables be submitted electronically in each of the source, electronic bid and web formats. The source format allows the government to reuse, edit, or otherwise manipulate the contents of the file except where the original file is a raster image, as in the case of product literature. The electronic bid-set format is best suited for creating electronic bid-sets which reduces the cost of distributing hard copy. The web format allows documents to be accessible, viewed and printed using a web browser.

1.2.3 CADD Standards

The CADD Standards section of the PRPEDS establishes the guidelines for preparing, organizing, managing, archiving, plotting and delivering CADD drawings including common drafting standards for the project. (See Section 2.0)

1.2.4 Text Document Standards

The Text Document Standards section of the PRPEDS establishes basic guidelines for text intensive documents. Examples of such documents include studies, reports, specifications, databases, operations and maintenance manuals, meeting minutes and correspondence. All text documents containing a table of contents (TOC) shall be indexed and hyperlinked to the first page of each section listed in the TOC Adobe’s indexing function. Compound text documents not including actual embedded CADD graphics shall contain a hyper-link that will launch the viewer and display the image. Below is the list of text document types and the corresponding electronic file formats required by the electronic standards.

ELECTRONIC DATA STANDARDS 5

Text Document Formats

Text Document Types Source Formats Electronic Bid/ Web Formats

Simple Text *Microsoft Word 2000 Adobe Acrobat Reader PDF 5.0

Compound Text (Small and Medium) *Microsoft Word 2000 Adobe Acrobat Reader PDF 5.0

Compound Text (Medium and Large) Microsoft Powerpoint 2000 Adobe Acrobat Reader PDF 5.0

Design Specifications Microsoft Word 2000 Adobe Acrobat Reader PDF 5.0

Spreadsheet *Microsoft Excel 2000 Adobe Acrobat Reader PDF 5.0

Presentation *Microsoft PowerPoint 2000 Adobe Acrobat Reader PDF 5.0

Raster JPEG Adobe Acrobat Reader PDF 5.0

Database *Microsoft Access 2000 Adobe Acrobat Reader PDF 5.0

Project Management (i.e. schedules) Primavera P3 Adobe Acrobat Reader PDF 5.0

*Bundled with the Microsoft Office 2000.

1.2.5 CPM Construction Schedule Standards

The scheduling method to be used shall be a Critical Path Method (CPM) schedule in the form of an activity on node Precedence Diagram Method (PDM) with capabilities of identifying the critical path. The principles and definitions of the terms used herein shall be as set forth in the Associated General Contractor's publication "CPM in Construction", latest edition.

The Contractor shall provide separate CPM schedule networks and sub-networks of activities for each process or facility. Each sub-network shall be assigned a code and separate activity numbering. The interrelationships between sub-networks and individual activities shall be identified.

1.2.6 Legacy Data

Issues of exceptions to the EDS due to technical limitations shall be listed as Legacy Data information with a description of technical limitations and justifications and submitted to Penren

ELECTRONIC DATA STANDARDS 6

for review and approval. Upon approval the exception shall then be included to the list of Legacy Data issues in the EDS. See section 5 Appendix C.

ELECTRONIC DATA STANDARDS 7

2 - CADD STANDARDS

2 CADD Standards

ELECTRONIC DATA STANDARDS 9

2.1 General CADD Information

2.1.1 Purpose

The purpose of this section is to provide CADD criteria and guidelines for all electronic CADD data produced for the PRP by All A/E/C Contractors and their Subcontractors, A/E/C contractors and their subcontractors. The PRPEDS CADD standards set basic CADD requirements that help to ensure consistency in architectural, engineering, and as-built drawings. Some key objects of this section of the standards are listed below:

• Individual drawings shall be clean and neatly organized.

• Drawings shall contain sufficient information to clearly indicate the design intent. Clarity of intent is enhanced by the use of a consistent graphical presentation.

• Related information shall be grouped together in the drawing set and be adequately cross-referenced.

• Standard drawing items such as north arrows, notes, titles, and key plan shall be placed in the same location on each drawing whenever possible.

• Consistency of "style" shall be evident across disciplines and throughout the entire drawing set.

• All drawing sets shall be produced by CADD software and shall have the same style or “look and feel”. The drawings should look as though each drawing was produced from a single source using common standards and parameters.

2.1.2 CADD Definitions

CADD and CAD - Computer Aided Design and Drafting software and hardware used in the design and production of contract drawings. Within the context of this document, CAD and CADD are equivalent terms.

CAE - Computer Assisted Engineering.

Design Sketch - Sketches that are used to illustrate design concepts or to clarify the design intent.

Generally, these sketches are freehand or rough drafted studies. Where a more precise drawing is required for analysis, electronic drafting should be utilized because this system will then provide the basis for further CADD development. Design sketches are retained for the record and should include the dates; names of the originator, drafter and reviewer; as well as the disposition of comments.

ELECTRONIC DATA STANDARDS 10

Approved Drawing - A drawing that has been reviewed and approved for content by the Government as well as reviewed, and approved for issue by the A/E Design contractor.

Contract Drawing - A drawing that is included in the construction awarded package. Within the context of this document, "contract drawing", "construction drawing", and “contract document” are equivalent terms.

Controlled Drawing (Change Notice/Orders) - A drawing for which a formalized change process for revisions/updates after initial issue is required.

Drawing Index - A spreadsheet in a word or excel format and a cad drawing which contains a comprehensive list of all drawings in sequential order along with the corresponding sheet number and drawing title. Large contract packages `that are divided into volumes shall be labeled accordingly, and contain a drawing index near the beginning of each volume.

General Drawing - A drawing that contains general information that is applicable to the full set of drawings. Typical information contained on a general drawing include: Cover sheet / Title sheet, Index of Drawings, Location Map, Abbreviations, Symbols, Legend, General Notes, Code Analysis, Project Data.

Detail Drawing - A drawing of a larger scale and greater detail which permits a more thorough understanding of the contract documents.

Contract Sheet File - An electronic drawing file prepared as the final contract drawing to create plots for construction documents. Within the context of this document, "contract drawing", "contract sheet", and “sheet” are equivalent terms.

Legacy Data – Electronic drawing files prepared in the early stage of the project in which the data does not completely comply with the EDS due to use of different CAD applications and versions.

3D Model File – CADD files that are identified by the initial letter of their names as ‘M’ contain an accurate three-dimensional representation of a design. These files are not referenced directly into the sheet files. These files are included in the extraction process and the extraction files created are then referenced into the sheet files.

Extraction File – MicroStation files that are identified by the initial letter of their names as ‘E’ and are created by an extraction process from a Microstation 3D Model to represent a flat 2 dimensional plan or section view. Extraction files are referenced into the Contract Sheet files.

Reference File – CADD files that are identified by the initial letter of their names as ‘X’ and are brought in as a reference file into the Contract Sheet files. These files are not included in the extraction process.

Concept Design – 35% - The concept design submittal shall include sufficient information to represent the overall size and character of the project based on the approved schematic design.

ELECTRONIC DATA STANDARDS 11

Preliminary Design - 75% - The preliminary design submittal shall incorporate the comments of the previous submittal and shall include the refinements of the building systems as they represent the overall size and character of the project.

Pre-Final Design – 95% - The pre-final design submittal shall include all the finished design to form the complete construction documents.

Final Design - 100% - The final design submittal shall incorporate all comments resulting from the 95% submittal review.

As-Built Record Drawings - Contract drawings (hard copy and CADD) that have been modified to include all changes that have been incorporated by amendments or modifications, and additional as-built conditions as recorded by the contractor. These documents represent the official project record of the constructed or installed facilities or systems.

As-Built Documents - Drawings, specifications, or field notes that are maintained by the construction contractor and Government Resident Engineer on a regular basis to reflect the actual location of all elements of the building and all of the systems in the building.

Reference Only Drawing - A document that is provided to the contractors for reference only for the purpose of supplying information which is relevant to the design of adjacent or related project facilities or systems. Reference drawings are marked "FOR REFERENCE ONLY, NOT FOR CONSTRUCTION". Reference drawings are not required to comply with these standards .

Reference drawings, in this context, do not refer to CADD reference files.

Imperial Units – The unit of measure for the contract documents, in feet and inches. In accordance with a directive from PenRen the HPCC team was permitted to do the project in Imperial units due to the compelling reason that the building was built in Imperial units as was the Phoenix reconstruction.

Shop Drawing - Detail drawings or other documents, which illustrate the individual items and components, that are utilized in the assembly of a specific item or structure and are prepared by the fabricator or vendor of those items. These documents must be checked and approved by the responsible contractor prior to their issuance to the A/E design contractor for their review.

Electronic Support Files - Files such as pen tables, color tables, cell libraries, parts libraries and plot files that are needed to produce contract drawings.

MicroStation - The CADD software program by Bentley Systems, Inc., MicroStation Triforma V8 (or higher) version, which produces the 2D and 3D design file format usually denoted with the file extension ‘DGN’. MicroStation is a registered trademark of Bentley Systems, Inc.

Cell - A cell is a complex symbol, notation, detail or group of elements (in effect, a small drawing) that can be stored in a file called a cell library, for repeated use in one or many drawings. Cells may include text and tags.

ELECTRONIC DATA STANDARDS 12

Cell Library - A file that contain cells. This file can be simultaneously shared by any number of design files, and users. The intent of cell libraries is to promote efficiency and consistency in the design process through reuse of resources.

Nested Cell - A cell that contains another cell. Nested cells are not to be used in any CAD files for the PRP.

Shared Cell - Cells placed within a drawing file that all share a single graphic definition. When a shared cell is replaced using the Replace Cell tool, all instances of the cell are replaced.

Drop Status - The operation of disassociating the graphical components from their grouping as a cell.

Terminator Cell - A cell used at the end of a linear element. The cell rotates to the angle defined by the last tangent section of the linear element. All cells can be used as a terminator.

Pattern Cell - A cell used in a repeated application along a linear element. Cells can also be used in repeated applications to pattern a closed area.

Point Cell - A cell that assumes the active symbology upon placement and is view independent.

Point cells shall not to be used in any CADD files for the PRP.

Graphic Cell - A cell whose symbology is determined when created and is view dependent (rotates with the view of which it is a part).

Tags – This is the process of attaching editable text attributes to graphic elements within a design file or as a cell, which can be extracted out as a report in a comma delimited format.

2.1.3 CADD Standards

The PRP requires that all CADD deliverables be in the .DGN format. Contractors will be responsible for any translations or editing required to meet the PRP Electronic Data Standards, if they use CADD platforms other than MicroStation. Any such translation or editing must preserve the accuracy and integrity of the original CADD file.

CADD File Formats

Document Type Source Format Electronic Bid Statement Web Format

CADD

Microstation V8 Triforma DGN or higher

PDF, Ver. 6.0 or higher, set to scale, with layer structure inherited from the source CAD file and 300 to 400 dpi resolution.

DPR

ELECTRONIC DATA STANDARDS 13

2.1.4 History of the CADD Standards

The previous CADD standard was based on U.S. Army Corps of Engineers (COE) Computer- Aided Design and Drafting (CADD) Systems Standard Manual dated 30 June 1990. This standard was rescinded by the COE on 30 June 1996 and not replaced. Around the same June 1996 time period, the Tri-Service organization (Air Force, Army, and Navy) published a pre-final draft of a new CADD standard called Tri-Service A/E/C CADD Standards. For these and other reasons, the PRPEDS CADD standards are based on the Tri-Service A/E/C CADD Standards.

The PRPEDS was used as a basis for the current EDS in order to maintain consistency between the existing drawing files prepared for the Wedge-1 project and the drawing files being prepared for the Wedges 2-5 project.

2.2 Coordinate System and Building Orientation

2.2.1 Maryland State Coordinate System

The MSCS has been chosen as the common orientation and coordinate system for the PRP. The MSCS was chosen as the standard coordinate system because all the monumental government buildings in the NCPC are on the MSCS as well.

The MSCS data for all disciplines are recorded below.

Lambert Conformal Conic (Two Parallel):

Origin Latitude: 37° 50’ 0.00000” N False Northing: 0.000 Parallel One: 39° 27’ N

Origin Longitude: 77° 00’ 0.00000” W False Easting: 800,000.000 Parallel Two: 38° 18’ N

2.2.2 Geographical and Non-Geographical Drawings

Contract drawings are categorized into two major types: geographical and non-geographical.

This distinction is made because there are some differences that occur when setting up and plotting each.

Geographical oriented drawings are those produced by Civil, Right-of-Way and Utilities disciplines and map on a one-to-one basis between these disciplines. Non-geographical drawings consist of plan, building, or model files wherein the drawing elements describe the spatial relationship of plans, elevations and sections with reference to established monument points for each project.

The location of objects with respect to ground coordinates, and the MSCS is critical. A/E/C contractors must maintain access to the MSCS for the life of the project and in all contract document files.

ELECTRONIC DATA STANDARDS 14

2.2.3 Global Origin

Positioned within the 3D model design files is a global origin. A design file's origin is important because it serves as the point from which all other elements are located and also confirms that all Triforma 3d elements including 3d Solids are within the area limited by the Trforma solids cube area predefined in MicroStation. Global Origins are typically defined (located) in a design file by the Cartesian coordinate system. The benefits of standardizing the location of a drawing's origin is most notable in the use of reference files where drawings must conjoin and in design disciplines, particularly mapping, where the origin's location determines the available drawing area. All reference files shall be brought in with Orientation as Coincident. The 3D model files must align with their common global origin. The global origin in this project is also used as the center of the designed coordinate points of the Pentagon (equal arm lengths and angles) defined in the MSCS as X= 1,296,445.970’, Y= 438,624.437’, Z= 0.0’.

2.2.4 PRP Monument Point

The PRP monument point is a National Geodetic Survey (NGS) brass disk benchmark set by the US COAST & GEODETIC SURVEY stamped “PENTAGON 1942” having a published NGVD 1929 elevation of 38.62 feet. The benchmark is located near the center of the south loading dock inside the building near the first column at an elevation of 38’-7.5”

Note: “Z” is defined as the elevation 0.00 feet above the National Geodetic Vertical Datum (NGVD) of 1929 or mean sea level so that all points in the CADD environment will read as positive numbers. The approximate coordinate locations (See NGS Data Sheet) are as follows:

PRP Monument Point (North and East)

X Y Z

395050.5 E 133513.0 N 38’-7.5”

PRP Monument Point (Latitude and Longitude 1927)

Direction Degrees Minutes Seconds

Latitude North 38 52 10

Longitude West 77 03 25

ELECTRONIC DATA STANDARDS 15

2.2.5 Pentagon Coordinate Points

2.2.5.1 SURVEY and DESIGN Coordinate Points

In addition to the PRP Monument Point benchmark, five survey points of the Pentagon have been established. The assumption here is that these points are to the exterior face of the wall above ground foundation at the center of each apex.

Note: The original survey points were taken based on the Virginia State Coordinate System using NAD 27 with units of feet-inches. The Government has converted this data to metric and mapped to MSCS using the CORPSCON V4.12 conversion program and then converted the data for MSCS imperial units. The Survey MSCS points are defined in the following chart for records.

All disciplines shall use the Design Coordinate Points as defined in the chart below for preparing Construction Documents (drawings, 3d models etc.). The design coordinate points have been established by holding the Wedge 2 corner of the 2002 Survey coordinates as the common point and developing a geometrically perfect Pentagon shape for design and construction purposes.

The assumption made is that the exterior face of the wall above ground is 18 inches outside the structural column grid ‘A’ in all directions. The 5 corners (apex) and the center of the Pentagon are defined by the Design Coordinate Points in the following chart.

PENTAGON

APEX

DESIGN

COORDINATE

POINTS

2002 SURVEY

MSCS POINTS

Wedge One N 438,279.940 N 438,279.498

E 1,295,739.608 E 1,295,740.388

Wedge Two N 439,189.735 N 439,189.735

E 1,295,899.842 E 1,295,899.842

Wedge Three N 439,318.486 N 439,319.366

E 1,296,814.624 E 1,296,814.619

Wedge Four N 438,488.263 N 438,489.271

E 1,297,219.756 E 1,297,220.802

Wedge Five N 437,846.406 N 437,846.628

E 1,296,555.360 E 1,296,556.742

ELECTRONIC DATA STANDARDS 16

PENTAGON

APEX

DESIGN

COORDINATE

POINTS

2002 SURVEY

MSCS POINTS

Center N 438,624.566

E 1,296,445.838

Centroid N 438,624.907

E 1, 296,446.500

2.2.5 Pentagon Floor Elevations

The following chart shows the top of slab elevations for each of the floors in Pentagon.

Pentagon Floor Elevations

Floor Name Elevation (Z)

Fifth Floor 88.00 feet

Fourth Floor 76.62 feet

Third Floor 65.25 feet

Second Floor 52.79 feet

First Floor 38.71 feet

Proposed Mezzanine Floor 26.98 feet

Proposed Basement Floor 15.91 feet

ELECTRONIC DATA STANDARDS 17

2.3 CADD File Organization

2.3.1 Project Folder Structure

The main project folder is defined by the three-letter Project Identifier (ie. A81) issued by the Government. Under the main project folder there shall be discipline specific folders defined by the discipline designator (ie. A81C, A81E). Each discipline designated folder shall contain all contract drawing files including related 3d models and support files for that discipline. If additional discipline designated folders are needed for a project, the Government must be notified in writing for approval.

See Folder diagram on Appendix C, Exhibit A.1.

2.3.2 3D Design File Organization

The 3D design file organization demonstrates the steps and the work process from 3D models to the final contract sheets.

See File Organization diagram on Appendix C, Exhibit A.1.

2.3.3 3D Model Files

3D Model Files starting with the letter ‘M’ is an accurate three-dimensional representation of the design. The 3D model shall be used as the primary design and drawing source to develop the contract sheets for Area Plan views. All 3D Model files shall be included in the extraction process. 3D Model files shall not be referenced directly into the Contract Sheets. The smallest module of a 3D model file shall be one area per floor, per project of the PENTAGON. Each project is divided into Areas separated by March-lines on the plan. Therefore, each project shall consist of multiple 3D model files per floor. Each of these 3D model files shall be referenced to create a complete 3D model.

2.3.4 Extraction Files

Extraction files (a flat 2D representation view in a direction) starting with the letter ‘E’ are created by electronically processing designated section marks placed on 3D model files. The extraction files shall be referenced into the contract sheet file for plotting. All extraction files shall be referenced to the sheet file as individual models. All reference shall be brought with ORIENTATION=Coincident, SCALE=1:1 (True Scale), NEST=0. A separate extraction file shall be made for each plane view. No work or editing shall be done on the extraction files but shall be on the related ‘M’ files. A new extraction shall be done from the updated ‘M’ files to replace the earlier extraction file and update the Contract Sheet.

ELECTRONIC DATA STANDARDS 18

2.3.5 Reference Files

Reference files starting with the letter ‘X’ shall be referenced into the Contract Sheets and shall not be included in the 3D Model extraction process.

A/E/C contractors shall use reference files to eliminate or reduce graphic data redundancy whenever possible. Use of reference files is important for efficient use of CADD and in assuring coordination both within a discipline and between disciplines. This is of particular importance in PRP projects where interrelated components are designed by teams under many separate contracts.

All reference files must be system and network directory structure independent when referenced to contract sheet files. Therefore, no files shall be referenced using a technique or function that results in the hard coding of the path of a reference drawing (i.e. do not enable the 'save full path' option when attaching a reference file).

Similarly, within a discipline files should be structured so that large scale detail information can be added to clipped portions of the design file plan, section, and elevation information. In this way, changes in the basic information are reflected throughout the contract set.

Inter-discipline plan files shall be attached with Orientation as Coincident and without scaling or repositioning and reorientation in the Design Model. If a rotated plot view is required the user shall attach the design file coincidentally in the Design Model and then rotate the view in the Plot Model to the desired orientation. The border shall be attached in the Plot Model. All reference file clipping shall be done in the Plot Model.

All files referenced in a project must reside in sub-folders (assigned for each discipline’s drawings) within the main project folder to ensure a complete archive of the project. Each discipline shall list it’s drawings per contract and the reference files as shown in Appendix C, Exhibit A.1. The DGN folder for each Discipline folder shall contain all it’s contracts sheets and related reference files including the related reference files from other disciplines.

Contractors shall not enable the "Save Full Path" option when attaching the reference files because this causes the relationship of the active files and reference files to be site specific.

Enabling the "Save Full Path" option also prevents files from being moved to different sub-directories should the need arise.

If it is necessary to define logical names when attaching reference files then the contract file name shall be used as the logical name using lower case letters. If a reference file has to be attached to the same active file more than once, simply add a pair of parenthesis "(#)" with a number indicating the occurrence of that file. For example, when the file xa81af01.dgn is attached to a81af02.dgn the first time, the logical name will be xa81af01. If it is attached a second time, its logical name will be xa81af01(2). If it is necessary to add a description then add a hyphen after the contract file name and then add a short description in the logical name.

ELECTRONIC DATA STANDARDS 19

All reference files temporarily attached to the sheet shall have a logical name ‘TEMP-01, TEMP- 02, TEMP-03 etc. All temporary reference files shall be detached from all contract sheet files before being submitted to the Government.

All reference files attached to a contract sheet file is identified by the display indicator checked in the references dialogue box and must be included on the electronic deliverable. All reference files shall have their displayed turned on and reference files not displayed shall be detached from the reference dialogue box.

When attaching a reference file, it is optional to fill in a complete description of the file that is being attached. However, if the contractor does decide to use this field, all reference files must contain the contract drawing title of the file that is being attached (e.g., ELECTRICAL PLAN - FIRST FLOOR) including the Wedge number. Descriptions for temporary reference files should indicate the reason the reference has been temporarily attached.

2.3.6 Contract Sheet Files

Contract sheet files starting with the letter ‘A’ are DGN files that contain information representing a contract drawing for plotting. Sheet files shall have VIEW 1 in the ‘PLOT MODEL” as the TOP view. All related reference files (‘X’ or ‘E’ files) shall be referenced to the sheet file in the model named ‘DESIGN MODEL’ using the default filename as the logical name. All reference shall be brought with ORIENTATION=Coincident, SCALE=1:1 (True Scale), NEST=0. Do not scale LineStyles (uncheck the box under options). Once all references are brought in then the sheet file shall be referenced to itself (self reference) with NEST=1 with SCALE as needed in the model named ‘PLOT MODEL’ using the same sheet file name as the logical name in VIEW 1 (which will be the TOP view). The Border file (xa81gb01) shall be referenced into this model with ORIENTATION=Coincident, SCALE=1:1 (True Scale), NEST=0. Multiple self reference with NEST=1 may be made to create multiple views at different scales on the Plot Model as necessary. This model named ‘PLOT MODEL’ shall be the final Contract Sheet view and shall be used for plotting. See exhibit A.? Each sheet file in the plot set shall be assigned a three digit Plate Number starting with 001 by the sequence in which the sheets will be organized for the printed hard copy set. All annotations, dimensions and notes shall be placed on the Area Plan Contract Sheet files.

2.4 Border File

The standard PENREN border file ‘xa81gb01.dgn’ (see reference file naming section) shall be used and referenced into the contract sheets for the entire project. The border file contains information that does not change throughout the project. Existing elements in the border file should not be modified. However, additional elements that will need to show on all drawings may be added to the border file if necessary. This file shall be referenced into the Plot Model of the Contract Sheet with ORIENTATION=Coincident, SCALE=1:1 (True Scale), NEST=0.

ELECTRONIC DATA STANDARDS 20

2.5 CADD File Identification

2.5.1 CADD File Naming Syntax

Naming conventions for CADD files assist CADD users in determining the contents of a file without displaying the electronic file. They also provide a convenient and clear structure for organizing drawing files within project sub-directories. The naming conventions provided within this manual are based on a twelve-character file name limitation required by PENREN. File names and extensions will be in lower case eliminating potential conflicts on UNIX file systems that differentiate upper and lower case characters. The file name components are as follows:

(1) Project Identifier

(2) Discipline Designator

(3) Discipline Modifier

(4) Sheet/Drawing Number

(5) New Sheet Identifier (6)File Name Delimiter

(7) File Extension

Detailed information about the CADD file naming syntax is given below:

2.5.1.1 Project Identifier

All files used in producing a contract drawing must have the correct project identifier. Counting from left to right, the first three characters of every file must be the project identifiers that are assigned to every project by the Government. A listing of current project codes is provided in Appendix C, Exhibit A.1. These codes are issued on a project-by-project basis. For example, the “a81” in a81af01_.dgn is the project identifier for the contract drawing set.

2.5.1.2 Discipline Designator

The fourth character of every file name must identify the discipline designator. For example, the “a” in a81af01_.dgn identifies an “architectural” file. A listing of discipline designators is provided in Exhibit A.3.

2.5.1.3 Discipline Modifier

The fifth character of every file name must identify the discipline modifier. The discipline modifier identifies a type of drawing within a major discipline designator (the fourth character).

For example, the “d”, in a81ad01_.dgn identifies a “demolition” file. A listing of discipline modifiers is provided in Exhibit A.3.

ELECTRONIC DATA STANDARDS 21

2.5.1.4 Sheet Number

Characters six and seven are numbers between 0 and 9. The sheet number is a number ranging from 01-99. The first file within a modified discipline (e.g., “ad”) shall begin with 01. For example, the “01” in a81ad01_.dgn is the first sheet in the architectural demolition section of drawings. For floor plans, the first digit is the floor and the second digit the area. In a81af52_.dgn, 52 is 5th Floor, area 2.

2.5.1.5 New Sheet Insert Identifier

The eighth character is the underscore “_”, the only non-alphanumeric character allowed in file names. This character is changed only if it becomes necessary to add sheet(s) late in the project, (i.e.. after the original project drawing index has been published). The underscore shall be replaced with a character starting with “a”, sequentially to “z”. For example, if you needed to insert a new sheet(s) between a81af01_.dgn and a81af02_.dgn, the new file name will be a81af01a.dgn. It should be noted that the file a81af01a.dgn is not a revised version of a81af01_.dgn file, but it is an entirely new sheet.

Note: The Tenant Sheets shall be named using the new sheet identifier so these sheets can be placed immediately after the Core & Shell 1/8 inch scale plan sheets of the same area. Since the total numbers of Core & Shell plan sheets are pre-determined, there should not be a need to use this New Sheet Insert Identifier for any insert other than the related Tenant Sheets.

2.5.1.6 File Name Delimiter

A period (.) shall be used to separate the file name from the three character file extension.

2.5.1.7 File Extension

All contract drawing files shall have the file extension ‘DGN’ after the file name delimiter ‘.’

Separating it.

2.5.1.8 3Dmodel File Name

All 3D files that will be included in the extraction process shall have a name starting with ‘M’ for example ‘ma81a_23.dgn’ where the prefix ‘m’ indicates that it is a 3D model file which will be extracted and referenced into a Contract Sheet. The next three characters are the ‘a81’ which is the project ID. The next prefix ‘a’ is the discipline designator. The next prefix ‘_’ is the discipline modifier which is left blank. The next prefix ‘2’ indicates the floor level. The last prefix ‘3’ indicates the area 3 (Each project is divided in areas). ‘M’ files shall not be referenced into the Contract Sheet files.

ELECTRONIC DATA STANDARDS 22

2.5.1.9 Extraction File Name

All extraction files shall be created by an extraction process from the ‘M’ files and shall have a name starting with ‘E’, for example ‘ea81af03.dgn’ where the prefix ‘e’ indicates that it is an extraction file. The next three characters are the ‘a81’ which is the project ID. The next prefix ‘a’ is the discipline designator. The next prefix ‘f’ is the discipline modifier with 2 digit numbers at the end. On the 1/8” scale Floor and Reflected Ceiling Plans the last 2 digits indicate the floor level. For example ‘ea81af0b.dgn’ indicates that it is the basement level. All extraction files shall be referenced into the sheet files.

2.5.1.10 Tenant Extraction File Name

All contract tenant extraction files be created by an extraction process from the ‘M’ files shall have a 9 character name for example ‘ea81af23a.dgn’ where the first prefix ‘e’ indicates that it is a extraction file. The next three prefixes ‘a81’ are the project ID. The next prefix ‘a’ is the discipline designator. The next prefix ‘f’ is the discipline modifier. The next prefix ‘2’ indicates the floor level, the next prefix ‘3’ indicates the designated area on that wedge (each project is divided into areas). The last prefix ‘a’ shall indicate a tenant partition layout. The last prefix ‘b’ shall indicate a tenant furniture layout. These tenant extraction files shall be referenced into the tenant contract sheets.

2.5.1.11 Reference File Name

All base reference files that are not related or created from the 3d model by extraction process shall have a name starting with ‘X’ for example ‘xa80af03.dgn’ where the prefix ‘x’ indicates that it is a reference file. The next three characters are the ‘a80’ which is the project ID. The next prefix ‘a’ is the discipline designator. The next prefix ‘f’ is the discipline modifier with 2 digit numbers at the end. On the Floor and Reflected Ceiling Plans the last 2 digit indicates the floor level. For example ‘xa80af0b.dgn’ indicates that it is the basement level. All base reference files will be referenced into the sheet files. When attaching a reference file, a logical name and description may be added as necessary.

Note: All reference files temporarily attached to the sheet shall have a logical name ‘TEMP’ to easily identify and remove them by an automated batch process for submission. All temporary reference files shall be detached from all contract sheet files before being submitted to the Government.

2.5.1.12 Tenant Reference File Name

All contract tenant reference files shall have a 9 character name for example ‘xa81af23a.dgn’ where the first prefix ‘x’ indicates that it is a reference file. The next three prefixes ‘a81’ are the

ELECTRONIC DATA STANDARDS 23

project ID. The next prefix ‘a’ is the discipline designator. The next prefix ‘f’ is the discipline modifier. The next prefix ‘2’ indicates the floor level, the next prefix ‘3’ indicates the designated area on that wedge (each project is divided into areas). The last prefix ‘a’ shall indicate a tenant layout plan. The last prefix ‘b’ shall indicate a tenant furniture plan. These tenant reference files shall be referenced into the tenant contract sheets.

2.5.1.13 ‘Contract Sheet’ File Name

All contract sheet files shall have an 8 character name for example ‘a81at23.dgn’ where the first three prefixes ‘a81’ are the project ID. The next prefix ‘a’ is the discipline designator. The next prefix ‘f’ is the discipline modifier. The next prefix ‘2’ indicates the floor level, the next prefix ‘3’ indicates the designated area on that wedge (each project is divided into areas). The last prefix is the ‘_’ (underscore).

The eighth character is the underscore “_”, the only non-alphanumeric character allowed in file names. This character is changed only if it becomes necessary to add sheet(s) late in the project, (i.e.. after the original project drawing index has been published) anywhere in the drawing set except for the 1/8” scale floor plan sheets (reserved for tenant sheets, see ‘Tenant Contract Sheet’ in the following section). The underscore shall be replaced with a character starting with “a”, sequentially to “z”. For example, if it is necessary to insert a new sheet(s) between a81at01_.dgn and a81at02_.dgn, the new file name will be a81at01a.dgn. It should be noted that the file a81af01a.dgn is not a revised version of a81at01_.dgn file, but it is an entirely new sheet.

2.5.1.14 Tenant ‘Contract Sheet’ File Name

All contract tenant Plan sheet files shall have an 11 character name for example ‘a81it23c12.dgn’ where the first three prefixes ‘a81’ are the project ID. The next prefix ‘i’ is the discipline designator. The next prefix ‘t’ is the discipline modifier. The next prefix ‘2’ indicates the floor level, the next prefix ‘3’ indicates the designated area on that wedge (each project is divided into areas).

For certain limited purposes, such as furniture procurement and installation plans that describe a specific demised area may be appropriate. In that event, the Tenant "Contract Sheet" File Name will be appended by the letter describing the Ring occupied by the tenant and a two-digit tenant identification number. For example, the file designation a81it23c12 would be used for a drawing that describes Tenant #12 in Ring C.

The…