3.3         General

3.3.1            Drawing Definitions

The following sections define general A/E/C drawing types.

3.3.1.1            Engineering Drawings

Engineering drawings are formal representations used to convey the physical and functional end product design and/or installation requirements of an item. They may include pictorial, graphical, schematic or textual presentations.

3.3.1.2            Construction Drawings

Construction drawings are engineering drawings, which show the design of buildings, structures, or the related construction, and are normally associated with the architectural, construction and civil engineering operations. Construction drawings establish all the interrelated elements of the pertinent services, equipment, utilities, and other engineering skills.

3.3.1.3            Installation Drawings

Installation drawings are engineering drawings, which show the installation requirements of equipment in facilities.

3.3.1.4            Space Allocation Drawings

Space allocation drawings are used to provide an accurate record of existing space, identify tenants and square footages of occupancy.

3.3.2            MDOT MAA AIRPortal PEGS Reference Documents Library

As a consultant performing services for MDOT MAA, it is assumed that individuals providing engineering services for MDOT MAA have an account to AIRPortal, MDOT MAA’s system of record. There are multiple applications and resources available through AIRPortal. One such resource is the PEGS Reference Documents library. Found in AIRPortal under General > PEGS Reference Documents, this library provides consultants and sub-consultants with access to the most current resources to prepare MDOT MAA-compliant products. Examples are:

A.      Logos

B.      Standard Borders

C.      Standard Title Sheets

D.      Layer Templates

3.3.3            Civil/SUE Confined Space Drawings

When a Civil or Subsurface Utility Engineering project includes either an inspection of existing confined space (CS) structures, or design of new CS structures, data regarding each structure shall be included in the contract drawings and associated digital data submissions. Consultants shall submit confined space CAD data at all design phases beginning with the 30% design phase (see PEGS V2, Chapter 3.2 Deliverables by Design Phase).

Before working with confined space data, consultants should be familiar with the MDOT MAA Confined Spaces guidelines in PEGS V7, Chapter 2 Confined Spaces, and the MDOT MAA GIS Standards in PEGS V1, Chapter 4 GIS Standards.

3.3.3.1            Submissions Format

Confined space data in CAD shall be entered in a dedicated AutoCAD .DWG file, attached to plan sheets as an external reference (xref) as needed. Each CS structure shall be represented by an AutoCAD block entity.

Two CS block definitions, named conf-spac and conf-space-prmt, have been pre-defined by MDOT MAA, and contain attribute definitions which must be populated by the consultant. Conf-space is to be used to represent unpermitted confined spaces, and conf-spac-prmt is to be used to represent permitted confined spaces.

Figure 3.3.3.1 examples of conf-spac.dwg and conf-spac-prmt.dwg

Click here to download conf-spac.dwg, or here to download conf-spac-prmt.dwg, two AutoCAD DWG2013 files which may be inserted into any existing AutoCAD file to represent CS structures.

3.3.3.2            AutoCAD Drawing Composition

Instances of the blocks conf-spac and conf-spac-prmt should be inserted on the appropriate layer. Instances representing existing CS structures may be inserted on layer C-CONF-EXST, while those representing new work may be inserted on layer C-CONF-NEWW.

The blocks conf-spac and conf-spac-prmt are dynamic blocks with multiple visibility states, each corresponding to a type of CS structure. After an instance of the block is inserted, the visibility state must be changed to indicate the type of CS structure it represents. By default, the block’s visibility state is set to EMH (electrical manhole).

The blocks also contain a set of AutoCAD Attributes, representing various types of data relating to CS structures. These attributes shall be populated by the consultant with all data known for each CS structure. See Section 3.3.3.4 Confined space attribute data for a list of these attributes.

3.3.3.3            Structure ID

Each CS structure shall be given a unique Structure ID by the consultant. This Structure ID will be confirmed by MDOT-MAA following submission at the Conformed design phase.

Structure IDs shall consist of five parts, separated by underscores or dashes, as illustrated in Figure 3.3.3.3.

Figure 3.3.3.3, Structure ID Format

·         SUE Grid ID: The first part of the Structure ID shall be the Grid ID of the 500’x500’ SUE grid name in which the structure is located (See PEGS V1, Chapter 1.5 Subsurface Utility Engineering (SUE) Data Requirements for AIRPortal).

·         Structure Type Code: The second part of the Structure ID shall be the applicable Structure Type Code (see Table 33.3.3 below). The structure type codes coincide with SUE Aliases. NOTE: Consultants may request that MDOT-MAA create additional structure type codes, as needed.

·         X Position: The third part of the Structure ID shall be the distance perpendicular to the west edge of the SUE grid containing the structure, to the center of the structure (i.e. the X-coordinate within the SUE grid), rounded to the nearest foot; should a structure’s center fall directly on the boundary between two SUE grids, it shall be assumed to be located in the grid to the west at position 000

·         NOTE: Parts three and four are separated by a dash rather than an underscore

·         Y Position: The fourth part of the Structure ID shall be the distance perpendicular to the south edge of the SUE grid containing the structure, to the center of the structure (i.e. the Y-coordinate with the SUE grid), rounded to the nearest foot; should a structure’s center fall directly on the boundary between two grids, it shall be assumed to be located in the grid to the north, at position 000

·         Date of Installation: The fifth part of the Structure ID shall be the month and year of the structure’s installation in MMYYYY format; this part shall not be added until the Record or As-Built design phase, following the structure’s construction

Click here to download  BWI_SUE_Grid.dwg, or here to download  MTN_SUE_Grid.dwg, two AutoCAD DWG2013 files containing the SUE grids for both airports.

Example Structure ID’s:

·         38-35_TMH_152-156_012003 - SUE grid 38-35, Telecommunications Manhole, position 152ft east by 156ft north, installed January 2003

·         38-33_EMH_069-219_122003 - SUE grid 38-33, Electrical Manhole, position 069ft east by 219ft north, installed December 2003

·         36-31_SWI_385-385_011988 - SUE grid 36-31, Stormwater Inlet, position 385ft east by 385ft north, installed January 1988

Table 3.3.3.3, Confined Space Structure Types and Codes

3.3.3.4            Confined space attribute data

The block conf-spac contains AutoCAD attribute definitions which must be populated for each CS structure. There is no AutoCAD attribute definition for Structure Type, since this data is represented by the block’s visibility state.

The attribute definitions within the block are all set to be invisible, to avoid creating visual clutter in the plan set. However, attribute values may be viewed and edited at any time by double-clicking an instance of the block, which will open AutoCAD’s Enhanced Attribute Editor.

Figure 3.3.3.4 AutoCAD Enhanced Attribute Editor

Table 3.3.3.4 Attributes defined in block conf-spac

3.3.3.5            GIS Data

Electronic deliverables for design projects include GIS data (see PEGS V2, Chapter 3.2 Deliverables by Design Phase and PEGS V1, Chapter 4 GIS Standards for details). GIS data will include a field denoting whether a structure is a confined space, which must be populated with a Confined Space - No Permit Required or Confined Space - Permit Required value for each structure that is a confined space and with Non Confined Space value for each structure that is not a confined space; see PEGS V1, Chapter 4.3 Attributes & Domains for details.