J-21 EDS Project Kickoff Presentation.pdf

1Facilities Services Directorate CUI November 19, 2024

Controlled By: FSD Controlled by: Integrated Technology Division (ITD) CUI Category: GCII Limited Dissemination Control: FEDCON POC: Michael P. Stebbing, (703) 424-4959

CUI

CUI

Washington Headquarters Services Facilities Services Directorate

Electronic Data Standards (EDS) Project Presentation

MPL: XX_XX

MONTH XX, 2024

2 Facilities Services Directorate CUI November 19, 2024

Agenda

• Introduction

• Integrated Technology Division Request Form

• ITD Provided EDS Documents

• GIS Standards

• Advanced Modeling Requirements

• Compliance Checklist Report

• EDS Review Supplemental Notes

• Submittal Folder Structure (EDS 3.2.2.)

• Example Index Sheet

• File Naming (A/E/C 2.4.2.)

• Reference Files (A/E/C 2.2.3.)

• Drawing Sheet Assembly (A/E/C 2.3.)

• Cells & Blocks (A/E/C 5.2.1.)

• Border File Requirements (A/E/C 2.2.2.)

• A/E/C Layers & Levels

• Common Deficiencies

• EDS Submittal Requirements

• Questions

3 Facilities Services Directorate CUI November 19, 2024

Electronic Data Standards

Introduction Who we are: We are the Integrated Technology Division (ITD), within the Facilities Services Directorate (FSD).

Location:

Physical: Room BF739

Objectives: The purpose of the EDS is to safeguard that the professional design deliverables (CAD, GIS, BIM, and Text Documents) used for construction are homogeneous, accurate, can be efficiently converted into effective As-Built deliverables to support Mission operations and maintenance, and future design work. FSD contractors shall ensure that all documents and all other contract deliverables covered in this standard are delivered per the appropriate electronic format(s) herein.

Contacts

• Help Desk: 703-614-1200

• Primary QA Specialist: TBD

• QA Specialist: Kelsey Riordan kelsey.e.riordan.civ@mail.mil

• Government contact: Jillianne Mattox jillianne.l.mattox.civ@mail.mil

4 Facilities Services Directorate CUI November 19, 2024

ITD Request Form

• Doc Printing

• EDS

• GIS Maps

• General Document

• Master Record Drawing

• Project RFI

• Site Validation

• Training

• Tririga Space Records

• Underground Utility

Length of Requests:

o 5 - 10 Business Days:

Document retrieval, Scanning (depends on size of request, how many disciplines and areas) o 5 Business Days: RFIs o 10 Business Days: EDS Compliance Reviews

5 Facilities Services Directorate CUI November 19, 2024

ITD Provided EDS Documents

We can facilitate secure transmission of the EDS package through DoD SAFE (Secure Access File Exchange)

Contents:

o EDS Project Presentation o WHS-FSD Pentagon EDS 6.1 o AEC National CAD Standards 6.1 o Index Sheet Sample o ITD Compliance Checklist o AutoCAD Design | Sheet Files o Border Samples Provided

6 Facilities Services Directorate CUI November 19, 2024

GIS Standards

Projection System: Geographical (Virginia State Plane North American Datum of 1983)

Dynamic Data formats: DGN, DWG, XLS, CSV, SHP, KML

Software: ESRI ArcGIS 10.x File stored as Geodatabase – Shapefiles

Standards:

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.

Civil CAD files, information, and data that is received that is already in compliance with AEC Standards can be more readily integrated into the SDSFIE Geodatabase.

Any standard not covered under Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE), will defer to Federal Geographic Data Committee (FGDC).

Metadata:

The SDSFIE-M v.2 Metadata Standard is a community standard for geospatial metadata and is a profile of the National System for Geospatial-Intelligence (NSG) Metadata Foundation, or NMF. NMF is, in turn, a profile of ISO 19115:2003/Cor 1:2006 (Geographic Information – Metadata). Is required for geospatial data.

7 Facilities Services Directorate CUI November 19, 2024

Advanced Modeling Requirements

• Required documents and Revit templates on applicable USACE Projects

• BIM Execution Plan (BxP) Template (USACE)

• Minimum Modeling Requirements Matrix (M3)(USACE)

• Revit Templates (Architectural, Mechanical/Plumbing, Electrical, Structural) (USACE)

• Facility Data Workbook (USACE)

• Facility Data PxP (USACE)

• All can be found on the USACE CAD BIM Center

• For all WHS projects, the insertion point is required to be set at 0,0,0 and located at the lower left column grid intersection. For existing projects, the insertion point should be the same as noted on the WHS reference drawings being used by the design team.

• (Please refer to the EDS Section 2.2.5 for more information regarding coordinate systems and building orientation).

8 Facilities Services Directorate CUI November 19, 2024

Submittal Folder Structure (EDS 3.2.2.)

• Submittal System:

o DoD SAFE o ProjNET o Other approved by ITD

• Folder Structure:

o Use provided folder structure for consistency across projects.

oRemove unused subfolders as needed.

oComplete accompanying index files.

“EXAMPLE”

9 Facilities Services Directorate CUI November 19, 2024

Example Index Sheet

• A spreadsheet for each discipline is required (Architectural, Mechanical, etc.)

• All file names and extensions in the discipline folder shall be included.

Building Name File Name Project Title Drawing Title Discipline Pentagon 12_345-A-FP-0100.dwg RENO 1F349 Architectural Floorplan Architectural Pentagon 12_345-A-FP-0100.pdf RENO 1F349 Architectural Floorplan Architectural Pentagon 12_345-E-LP-0100.dwg RENO 1F349 Electrical Lighting Plan Electrical Pentagon 12_345-E-LP-0100.pdf RENO 1F349 Electrical Lighting Plan Electrical

Model File Type Drawing Submission Submission Date Sheet Number MPL Number Floor Plan As-Built Submission January 1, 2023 A-FP-100 12_345 Floor Plan As-Built Submission January 1, 2023 A-FP-100 12_345 Lighting Plan As-Built Submission January 1, 2023 E-LP-100 12_345 Lighting Plan As-Built Submission January 1, 2023 E-LP-100 12_345

10 Facilities Services Directorate CUI November 19, 2024

File Naming (A/E/C 2.4.2.)

Model File Naming Convention

(1) Master Project List # – “23_001” in 23_001-A-FP-0100-Sheet#.dwg Note: Master Project List (MPL)# will be provided to you by ITD.

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

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

(4) Model Type Modifier:

“r” in r23_001-A-FP-0100.dwg Architectural reference file, 0100 model designator (See Table 2-4)

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

6-20 Character MPL# Discipline Designator Model File Type Sheet Type Designator Contractor Sheet Number

Sheet File Naming Convention

(1) Master Project List # – “23_001” in 23_001-A-101-Sheet#.dwg Note: Master Project List (MPL)# will be provided to you by ITD.

(2) Discipline Designator - “A” in 23_001-A-Sheet#.dwg Architectural

(3) Sheet Type Modifier:

in 23_001-A-101.dwg/pdf Contractor provided Sheet #

11 Facilities Services Directorate CUI November 19, 2024

Completeness vs Compliance

Sheet Type Designator Format Required 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 PDF Y Schedule 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

12 Facilities Services Directorate CUI November 19, 2024

Reference Files (A/E/C 2.2.3.)

• All reference files being used must be displayed Any reference files that are not used should be detached

• All references shall be an overlay and not an attachment

• Do not bind reference files to the drawing file

• Use relative path association

• An “r” designator will be placed in front of reference files (eg. r23_001-A-FP-0100).

• References should only be submitted in their respective discipline folders.

13 Facilities Services Directorate CUI November 19, 2024

Drawing Sheet Assembly (A/E/C 2.3)

• Proper drawing assembly supports a focused review of pertinent content. Model files and border sheet model files shall be assembled as per figure below

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

• All reference files shall be stand-alone model files. Examples are Architectural backgrounds, Electrical work, Mechanical work, etc.

Mechanical HVAC Plan Design Drawing Model File

Border Sheet Model File

Mechanical HVAC Plan Sheet File Architectural Floor Plan

Design Drawing Model File

HVAC Plan Drawing Model

HVAC Plan Sheet Model

14 Facilities Services Directorate CUI November 19, 2024

Cells & Blocks (A/E/C 5.2.1)

• No models shall be inserted into another model as a block, models shall be referenced in.

• Cells/Blocks are the collection of geometries that act as a single object and they can be used in a drawing repetitively, they are not intended to be used as reference drawings in the design model

• Convert 3D blocks to 2D using defined conversion methods resulting in 2D line work that is easy to manage and integrate

• Use defined settings when transmitting a drawing set to maintain folder structure and stand-alone reference files.

15 Facilities Services Directorate CUI November 19, 2024

Border File Requirements (A/E/C 2.2.2.)

• Please maintain title block/border files as a reference

• All referenced image files used in title block/border file should be displayed (Logos, etc.)

• Fill out title block/border file with correct project information (Project Title, Submission date, MPL #, scale, etc.)

• ITD provided title block/border file provides correct format for security markings (CUI)

16 Facilities Services Directorate CUI November 19, 2024

A/E/C Layers & Levels

• A detailed definition for each layer, color, and layer style is shown in the provided table in AEC Appendix A

• If there is a layer/level you need that is not in the EDS, you can submit an RFI to get those layers/levels approved. (Provide all the information including Name, Description, Line Style and Line Color when submitting the RFI)

• All supplemental drawings provided by WHS or Other Source used as part of design excluding reference files must conform to EDS layer naming convention by IFC submission

17 Facilities Services Directorate CUI November 19, 2024

EDS Submittal Requirements

• Include your self-assessment COMPLIANCE CHECKLIST

• All Submissions are to be in the following file formats:

• .DWG

•.PDF

• All deliverables shall be submitted in 2D format only

• All AutoCAD, and alternative native primary software formats used to generate a submission need to be included for complete representation of all associated project content (e.g., Revit, Bentley Map, OpenBuildings Designer, Civil 3D, etc.)

• Include completed index files provided

• Appropriate drawing assembly

• Ensure A/E/C provided layers names are used

• Appropriate title block/border file

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

COR/LCPM

18 Facilities Services Directorate CUI November 19, 2024

Compliance Checklist Report eFIC QUALITY ASSURANCE CAD COMPLIANCE CHECKLIST REVIEW

Project Information

MPL # [MPL #]

Project Name (Provided by Government Contact) Project Title <found on Transmittal>

Submission Status 30% / 90% / 100% / IFC / As-Built Submission

Submission Date <found in eMail or Transmittal>

QA Review Date <date of Review>

Contractor/Sub Contractors Prime Company Name/ Sub Contractors

CAD Software and Version CAD Software and version used to create or manipulate drawings: AutoCAD v20## | MicroStation V8i/CONNECT

Reviewer Contact Information

Name

Email

Phone

Phase 1: Submittal Delivery Compliance Review 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 shouldbe 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

Phase 2: Spot Check File Structure Requirements Title & Revision Blocks The titleblock and revision block are correctly filled out: NA | No | Yes

All CAD files marked:

CUI (Controlled Unclassified Information)

All eFIC 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

MicroStation Working Units = Resolution: 304800 per Distance Foot The Design File Settings for Working Units is followed: 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-referenced files) An "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

Phase 3: Detailed CAD File Compliance Checklist

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 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 eFIC Quality Assurance CAD Compliancy Review Summary =NON-COMPLIANT | NON-CONFORMING |

COMPLIANT

19 Facilities Services Directorate CUI November 19, 2024

EDS Review Supplemental Notes

• The accompanying supplemental notes give further insight as to what is needed for compliance.

• Deficiencies are color coded as follows:

•MAJOR – These deficiencies directly impact integration and future project efforts. Contractor to remedy these items before next submission

• Non-compliant folder structure, file naming convention

• Missing Index files

• Missing CAD files and/or PDF files

• Missing background reference files

• Non-compliant use of references or blocks

• Non-compliant layers

•MODERATE – These deficiencies moderately impact integration and future project efforts.

Contractor to remedy these items before final submissions

• Non-Compliant Title block/border file

• Items on compliant but incorrect layers

• Discrepancies between index file names and actual file names

• Objects in design model beyond scope of design area

•MINOR – These deficiencies affect integration and future project efforts

• Existing and new work layers. These layers must be approved by using RFI reviewed by ITD and approved by the project COR/LCPM.

20 Facilities Services Directorate CUI November 19, 2024

Common Deficiencies

• Non-compliant file naming convention, and folder structure

• Items on compliant but incorrect layers

(eg. Electrical text on E-POWR-PANL instead of E-POWR-IDEN, etc.)

• Non-compliant layer names

• Missing reference files

• Non-compliant use of blocks

• 3D converted objects with too much detail or missing line work

• Objects in design model exceeding scope of design

21 Facilities Services Directorate CUI November 19, 2024

Questions