J-22 FSD Electronic Data Standards_6.1.pdf

Washington Headquarters Services

Department of Defense

AUTHORIZED BY:

Electronic Data Standards (EDS)

Facilities Services Directorate (FSD)

Integrated Technology Division (ITD)

Help Desk: (703) 614-1200

Version 6.1 ftJ.-f?

Robert G. Salesses

(A) Director, Facilities Services Directorate

26 March 2024

Table 1: Revision History

Date Description File Name

12 Jul 2019 Government review with inhouse contract team General EDS version 5.1

14 Aug 2020 ECM General Requirements Update General EDS version 5.2

28 Feb 2023 Updating for Pentagon Facility Guide Specifications

General EDS version 6.0

26 Mar 2024 Elevate to FSD-wide SOP General EDS version 6.1

Table of Contents

1.0 REFERENCES

2.0 FOREWARD

2.1 HISTORY

2.2 PURPOSE

2.3 SCOPE

3.0 CAD BIM TECHNOLOGY CENTER

3.1 CAD BIM TECHNOLOGY CENTER WEBSITE

3.2 CAD BIM TECHNOLOGY CENTER WEBSITE INSTRUCTIONS

4.0 REQUIREMENTS

4.1 GEOREFERENCING, RELATIVE ORIGINS AND UNITS

4.1.1 Interior Deliverable: Non-Geographical Drawings (Global Origin)

4.1.2 Exterior Deliverable: Geographical Drawings

4.2 COMPUTER AIDED DESIGN (CAD)

4.2.1 CAD DELIVERABLES

4.2.2 FOLDER STRUCTURE

4.2.3 FILE NAMING

4.2.4 DRAWING SHEET ASSEMBLY

4.3 KEY MAP REFERENCE

4.4 GEOGRAPHICAL INFORMATION SYSTEM (GIS)

4.4.1 SDSFIE 5.x.x

4.4.2 FGDC-STD-007.4-2002

4.4.3 GIS DELIVERABLES

4.5 BUILDING INFORMATION MODELING (BIM)

4.6 INDEX FILE

5.0 REQUIREMENTS FOR ELECTRONIC DELIVERY

5.1 COMPLIANCE CHECKLIST

5.2 DELIVERY MEDIA PREPARATIONS

5.3 HELP SECTION

5.4 DELIVERY PROCESS

ATTACHMENT

1.0 REFERENCES.

1.1. DoD Directive 5110.04, Washington Headquarters Services, 27 Mar 2013.

1.2 Architect/Engineer/Contractor (A/E/C) Computer Aided Design Standard 6.1 (A/E/C 6.1)

1.3 Pentagon Facility Guide Specifications (PFGS)

1.4 DoD Instruction 8130.01, Installation Geospatial Information and Services, 4 Aug 2020.

1.5 Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE 5.x.x)

1.6 Federal Geographic Data Committee Standard (FGDC-STD-007.4-2002)

2.0 FOREWARD.

2.1 HISTORY.

The WHS/FSD/ITD has the responsibility of updating and maintaining the EDS (reference 1.1). This standard incorporates, where appropriate, the latest A/E/C 6.1 developed by the CAD/Building Information Modeling (BIM) Technology Center (reference 1.2).

2.2 PURPOSE.

The purpose of the EDS is to establish that the design deliverables used for construction are homogeneous, accurate, and efficiently converted into effective As-Built deliverables to support operations and maintenance, and future design work. Professional design deliverables applicable to the EDS are Portable Document Format (PDF) files natively prepared in either CAD, Geographical Information System (GIS), or spreadsheet. FSD requires that all documents and all other FSD contract deliverables covered in this standard are delivered in the appropriate electronic format(s) as described in these standards.

2.3 SCOPE.

These standards are contained in the PFGS (reference 1.3), are contractually binding, and apply to all design, alterations, or construction projects at WHS-managed facilities. The EDS identifies four types of applicable electronic documents: BIM, CAD, GIS, and index spreadsheets. Prior to a project start, ITD will host an EDS review meeting to present the EDS and provide supporting documentation. If the EDS requirement identified cannot be achieved due to technical limitations of related hardware and/or software applications, then the Contractor must submit a Request for Information (RFI) to the Contracting Officer’s Representative (COR) to seek relief from specific numerated components of the EDS.

3.0 CAD BIM TECHNOLOGY CENTER.

3.1 CAD BIM TECHNOLOGY CENTER WEBSITE.

The CAD BIM Technology Center website is a resource for the full standards documents for CAD and BIM: https://cadbimcenter.erdc.dren.mil/

3.2 CAD BIM TECHNOLOGY CENTER WEBSITE INSTRUCTIONS.

This website can be logged into using CAD certification (preferred). If the user does not have a CAC, they can register for a login and password.

Image 1: Showing specific BIM/CAD screen for A/E/C 6.1 download.

4.0 REQUIREMENTS.

4.1 GEOREFERENCING, RELATIVE ORIGINS AND UNITS.

Contract drawings are categorized into two major types: geographical and non-geographical. Geographical (Exterior/Civil) oriented drawings use the local coordinate system (North American Datum of 1983). Non-Geographical (Interiors/Architectural) drawings use x,y,z coordinates of 0,0,0. For more detail refer to section “2.1 – Design Area” in A/E/C 6.1.

4.1.1 Interior Deliverable: Non-Geographical Drawings (Global Origin).

Positioned within every electronic drawing file is an origin point in AutoCAD. The required global origin for two-dimensional (2D) files in AutoCAD is x=0 and y=0.

Pentagon: The center of the Pentagon courtyard is Global Origin of x=0 and y=0 (x,y = 0,0). When three-dimensional (3D) files are used, the z-origin should be set to allow for elevations below 0.

Mark Center: The Mark Center origin point (0,0,0) is at the center of the northwestern steel post of the west tower building at grid A1.

Other WHS Facilities (Pentagon Reservation, RRMC, Leased Facilities): We require the global origin (x,y = 0,0) be placed at the southwestern corner of the main structure.

4.1.2 Exterior Deliverable: Geographical Drawings.

The State Plane Coordinate System (SPCS), which is only used in the United States, is a plane coordinate system (north-south and east-west lines are perpendicular) in which each individual state has between one to six zones, depending on the state's size and shape. The standard unit of measure for WHS to be used is the US survey foot.

Pentagon and Mark Center: Virginia North State Plane – North American Datum 83 (NAD83) Virginia North Federal Information Processing Standards (FIPS) 4501 (US Feet).

Other WHS Facilities: NAD83 with Appropriate State Zone if the elements reside within (US Feet).

4.2 COMPUTER AIDED DESIGN (CAD).

The CAD Standards section of the FSD EDS establishes the guidelines and procedures for preparing, organizing, managing, archiving, plotting, and delivering CAD drawings, including common drafting standards for the project. The A/E/C CAD Standard addresses topics such as presentation graphics, layer assignments, electronic file naming, and standard symbology. Users are required to use AutoCAD (.dwg) files for project support.

4.2.1 CAD DELIVERABLES.

The Contractor shall submit all deliverables in AutoCAD (.dwg), PDF, and the native format if other than AutoCAD (for example, MicroStation, Revit, Bentley Map, Open Buildings Designer). All design files shall be submitted using AutoCAD (.dwg) while all sheet files shall be submitted in PDF. All BIM deliverables shall be delivered in 3D and 2D formats. Additional 3D formats will require approval of the Contract Officer.

The Adobe PDF electronic copy shall be submitted as defined and received by the

COR.

ITD will provide the Contractors the Directory Structure and files to support a consistent working environment, configurable by the designer to assemble and organize their drawings and project files effectively and efficiently. The Directory Structure, templates with related data files, sheet files, and support files (i.e., seed files), layer/level files, libraries, tools, script files, etc., shall be delivered to the government.

Project CAD deliverables will be due at the ~35%, ~65%, ~95%, ~100%, Issued For Construction (IFC), and As-Built milestones.

4.2.2 FOLDER STRUCTURE.

ITD will provide the Contractors the Directory Structure and files to support a consistent working environment, configurable by the designer to assemble and organize their drawings and project files effectively and efficiently. The Directory Structure, templates with related data files, sheet files, and support files (i.e., seed files), layer/level files, libraries, tools, script files, etc., shall be delivered to the Government.

4.2.3 FILE NAMING.

The file naming of the CAD, PDF, and any other native file equivalents shall be as shown in the chart below:

Image 2: Example File Naming Convention

1. Master Project List # – “24_001” in 24_001-A-FP-0100-Sheet#.pdf.

Note: Master Project List (MPL)# will be provided to you by ITD.

2. Discipline Designator - “A” in 24_001-A-FP-Sheet#.dwg Architectural Floor Plan.

3. Model File Type- “FP”, in 24_001-A-FP-Sheet#.dwg Architectural Floor Plan.

4. Model Type Modifier “r” in r24_001-A-FP-0100.dwg/ Architectural reference file, 0100 model designator (See Table 2-4).

5. Sheet Type Modifier: in 24_001-A-FP-0100-A100.pdf Contractor provided Sheet #.

2 4 _ 0 0 1 – A – F P – 0 1 0 0.dwg

6-20 Character MPL#

Discipline Designator

Model File Type

Sheet Type Designer

Contractor Sheet Number

Table 2: Master Record Drawing Disciplines.

Discipline Design File Name

Architectural Floorplan A-FP-F# Architectural Reflected Ceiling A-CP-F#

Electrical Information Management & Technology (IM&T) E-IM&T-F# Electrical Lighting E-LP-F# Electrical Power E-PP-F#

Fire Protection Fire Alarm/Detection F-FA-F# Fire Protection Fire Suppression F-FP-F# Fire Protection Life Safety F-LP-F#

Interiors Furniture I-RP-F# Mechanical Heating, Ventilation, and Air Conditioning (HVAC) M-HP-F# Mechanical Hot/Chilled Water (HTCW) Utilities M-HT-F# Plumbing Piping P-PP-F# Structural Column S-CP-F# Structural Foundation S-FN-F# Structural Framing S-FR-F#

Table 3: Design Type Requirements.

Design Type Designator Format Retained For Completeness

Required for EDS Compliance

General (symbols legend, notes, etc.)

0 DWG Y

Plans (horizontal views and combination plan and profile)

1 DWG Y Y

Elevations and profiles (vertical views)

2 DWG Y

Sections (sectional views, cross sections, etc.)

3 DWG Y

Large scale views (Scaled up reproductions of plans, elevations, or sections that are not details)

4 DWG Y Y

Details 5 DWG Y

Table 3: Continued.

Design Type Designator Format Retained For

Completeness Required for EDS Compliance

Schedules and diagrams 6 Digital (Excel, Visio, Other)

Y

Libraries, fonts, … N/A Digital Y

User defined N/A Digital Optional

3D Representations (isometrics, perspectives, photographs)

N/A Digital

(PDF, JPG)

Y When defined in Statement Of Work

PFGS 01 30 00 3.4 RFI: The Contractor must use the Government provided RFI template and fill in all requested information. For questions regarding the EDS, submit an RFI.

4.2.4 DRAWING SHEET ASSEMBLY.

Proper drawing assembly is required based on A/E/C Section 2.3. Model files and border sheet model files shall be assembled as per figure below.

Image 3: Proper Drawing Assembly.

Contractors shall utilize CAD software and adhere to using the Design models to maintain all essential discipline elements and use the plot sheet or layout to store/show dimensioning, symbols, and construction notes.

Compliance reviews for CAD submissions will review the content in the model space of the Design Files. The contractor will be responsible for producing compliant paper space content. The contractor shall coordinate with ITD for the latest software format or version available to the government. Refer to geographical standards identified herein where applicable.

All reference files shall be standalone model files. Examples are architectural backgrounds, electrical work, mechanical work, etc.

4.3 KEY MAP REFERENCE.

Projects that require EDS compliance are often reviewed and referenced by building engineers for the Pentagon. To provide efficient referencing of project locations, ITD requires the use of the Pentagon “Key Map”. It is required in two locations.

ITD will provide the Key Map Design File (G-GC-KM.dwg) to be referenced to the applicable design models of the project. The design models will show only the areas of interest that the project impacts.

In addition, the title block will contain a key map with the applicable areas of interest shaded. The title blocks will be provided at the beginning of the project.

4.4 GEOGRAPHICAL INFORMATION SYSTEM (GIS).

Per reference 1.4, standards and specifications are essential to facilitate the development and sharing of geospatial data and products. The GIS Standards section of the FSD EDS establishes standards and specifications define requirements to ensure that all maps and data prepared for and by FSD, in support of the Master Record Drawings, are consistent in accuracy, structure, format, style, and content. All GIS documentation shall adhere to geographical standards identified herein. Any standard not covered under Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE), will defer to the Federal Geographic Data Committee (FGDC).1

4.4.1 SDSFIE 5.x.x2.

The SDSFIE (reference 1.5) is the DoD family of spatial standards and models that supports common implementation and maximizes interoperability for installation, environment, and civil work missions.

4.4.2 FGDC-STD-007.4-2002.

Apply FGDC Standards (reference 1.6) when SDSFIE standards are not applicable to geospatial data sets developed. Part 4 provides accuracy standards for engineering drawings, maps, and surveys used to support planning, design, construction, operation, maintenance, and management of facilities, installations, structures, transportation systems, and related projects. It is intended to support geospatial mapping data used in various engineering documents, such as A/E/C drawings, site plans, regional master planning maps, and related Geographical Information System (GIS), Computer-Aided

1 https://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part4/FGDC-endorsed-standard 2 https://www.sdsfieonline.org/

Drafting and Design (CADD), and Automated Mapping/Facility Management (AM/FM) products. These products are typically created from terrestrial, satellite, acoustic, or aerial mapping techniques that output planimetric, topographic, hydrographic, or feature attribute data.

4.4.3 GIS DELIVERABLES.

The Contractor shall produce all drawing submittals in Environmental Systems Research Institute (ESRI) ArcGIS Professional Version 3.x or higher or ESRI ShapeFile (SHP). All electronic submittals shall be georeferenced according to the guidelines set forth in section 4.0. The Contractor shall submit drawings in Adobe PDF.

4.5 BUILDING INFORMATION MODELING (BIM).

BIM deliverables are defined by the project’s scope of work and will vary. FSD’s integrated project team, information resource center, government project managers, government contract officers, A/E/C contractors, subcontractors, editors, document authors, CAD specialists, and designers involved with FSD are responsible for ensuring that electronic deliverables conform to these standards. The contractor shall coordinate with ITD for the latest software format/version available to the government. All CAD and GIS deliverables produced using BIM software shall conform to the requirements set forth in this document. Upon contract award, government contractors are responsible for compliance with these standards.

4.6 INDEX FILE.

A set of digital drawing indices are required for each submission in spreadsheet format. An index file is required for each applicable drawing discipline and all files included in the folder shall be listed with the correct file extensions. The discipline specific index files are provided at the beginning of each project. See sample tables with required information below:

Table 4: Examples of Spreadsheet Information.

Building Project Number Project Name Submission Submission Date

Pentagon 12_345 RENO 1F349 As-Built 1 Jan 2024

Pentagon 12_345 RENO 1F349 As-Built 1 Jan 2024

Discipline Design Sheet Number File Name

Architectural Floor Plan A-FP-100 12_345-A-FP-0100.dwg

Electrical Lighting Plan E-LP-100 12_345-E-LP-0100.pdf

5.0 REQUIREMENTS FOR ELECTRONIC DELIVERY.

5.1 COMPLIANCE CHECKLIST.

Contractors shall complete the “Compliance Checklist” form per each deliverable package.

Submissions provided to the government with an incomplete Compliance Checklist will be found NON-COMPLIANT. A copy of the required Compliance Checklist is attached.

The purpose of the EDS is to archive and safeguard that the professional design deliverables (CAD, GIS, BIM, and Index Spreadsheet) used for construction are homogeneous, accurate, and can be efficiently converted into effective As-Built deliverables to support Mission operations, maintenance, and future design work. Rejected final submittal files shall be fixed and returned within a period specified in contractor’s contract.

5.2 DELIVERY MEDIA PREPARATIONS.

Perform the following procedures:

Include your self-assessment COMPLIANCE CHECKLIST REPORT

Include A/E/C Directory Structure Folder and all subsequent files, both graphic and non-graphic, required for the project, templates with related data files, sheet files, and support files (i.e., seed files), layer/level files, libraries, tools, script files, etc., shall be delivered to the government

Remove all extraneous graphics outside the border area and set the active parameters to a standard setting or those in the seed file

Ensure all reference (external reference) files are attached without device or directory specifications

Provide completed index files

Use A/E/C provided layers names

Document any nonstandard items using RFI form, reviewed by ITD and approved by the

COR.

5.3 HELP SECTION.

Providing Civil information models (Civil 3D):

https://www.youtube.com/watch?v=gteuEV81yrU https://knowledge.autodesk.com/support/civil-

3d/troubleshooting/caas/sfdcarticles/sfdcarticles/Civil-3D-Dependencies-are-not-included-in-ETRANSMIT-in-Civil-3D.html?us_oa=akn-us&us_si=7a393562-c078- 44df-b6d9-6af96735782f&us_st=eTransmit%20for%20Civil3D

Architectural information models (Revit):

https://www.youtube.com/watch?v=hyIsL0-tVr4 https://knowledge.autodesk.com/support/revit/learn-explore/caas/CloudHelp/cloudhelp/2019/ENU/Revit-AddIns/files/GUID-2317F99F- 070C-4D05-A37B-5D9488B35376-htm.html

Renaming Layers in AutoCAD:

https://www.autodesk.com/blogs/autocad/autocad-layer-translator-tuesday-tips-with-frank/

5.4 DELIVERY PROCESS.

Coordinate with Project Manager and/or Project Coordinator to upload submissions to the project folder in ProjectWise.

MPL #

Project Name (Provided by Government Contact)

Submission Status

Submission Date

QA Review Date

Contractor/Sub Contractors

CAD Software and Version CAD Software and version used to create or manipulate drawings: AutoCAD v20##

Name

Email

Phone

Sheet File Checklist: Description EDS COMPLIANT

Folder Structure

EDS Directory Structure Folder and all subsequent files, both graphic and non-graphic, required for the project (e.g., seed/template files, cell libraries, dgnlib files, etc.) provided at project kick-off is followed:

NA | No | Yes

Project File Index of Drawings Spreadsheet Included A drawing index spreadsheet for all files is provided: NA | No | Yes

PDF Submission Included All sheet file deliverables should be in PDF format: NA | No | Yes

Six-digit Alphanumeric Project ID Prefix used in File Names: 23-001…A six-digit project identifier prefix on all CAD files is used: NA | No | Yes

EDS File Naming: 2 3 _ 0 0 1 – A – F P – 0 1 0 0 The WHS EDS file naming convention is followed: NA | No | Yes

Title & Revision Blocks The titleblock and revision block are correctly filled out: NA | No | Yes

All CAD files marked:

CUI (Controlled Unclassified Information)

All ITD documents are appropriately identified, marked, stored, and accounted for as outlined in DoDM 5200.01:

NA | No | Yes

AutoCAD Drawing Units = Length Type: Architectural The Drawing File Settings for Drawing Units is followed: NA | No | Yes

Global origin and Georeferenced coordinates:

Design model global origin = 0,0 and set to NAD 83 or Virginia North FIPS 4501 State Plane coordinate system

NA | No | Yes

Raster files displayed = On All raster files being used are displayed: NA | No | Yes

Raster files unused = Removed Extraneous raster files are removed (red highlighted files): NA | No | Yes

Reference/xref files prefixed with "r": r23-001-… (non self-referencedAn "r" was placed in front of all individual reference files: NA | No | Yes

Reference/xref files displayed = On All reference files being used are displayed: NA | No | Yes

Reference/xref files unused = Removed Extraneous reference files are removed (red highlighted files): NA | No | Yes

EDS Level/Layer Names The level naming convention should be as the example given in Appendix A of the AEC CAD Standards v6.1.

Levels not named accordingly are to be removed.

NA | No | Yes

EDS Cells/Blocks No models shall be inserted into another model as a block, models shall be referenced in.

NA | No | Yes

EDS Design Models

No background information (Architectural, etc.) shall be live in a discipline specific design model. Background information shall be placed in its own design model which is referenced into the discipline specific design model.

NA | No | Yes

NONCOMPLIANT | NON-CONFORMING |

COMPLIANT

Government Sponsor Approval Signature and Date:

ATTACHMEMT

ITD QUALITY ASSURANCE CAD COMPLIANCE CHECKLIST REVIEW

Project Information

[MPL #]

ITD Quality Assurance CAD Compliancy Review Summary =

Phase 3: Detailed CAD File Compliance Checklist

Phase 2: Spot Check File Structure Requirements

Phase 1: Submittal Delivery Compliance Review

Prime Company Name/ Sub Contractors

<date of Review>

Project Title <found on Transmittal>

35% / 65% / 95% / 100% / IFC / As-Built Submission

<found in eMail or Transmittal>

Reviewer Contact Information

AS OF 05 MARCH 2024