1.5 Subsurface Utility Engineering (SUE) Data Requirements for AIRPortal
Prior to submitting a fee proposal for a project at BWI Marshall and MTN Airports, consultants are required to coordinate with their MAA Project Manager and the GIS & Engineering Technology Section (GETS) to identify the requirements for Subsurface Utility Engineering (SUE). Projects that typically require SUE include, but are not limited to, projects that may require: excavation, installation of new utilities, relocation of existing utilities, and/or building a new structure/facility.
SUE is not limited to identification and disposition of existing underground utilities. Accordingly, existing aboveground utilities, such as storage tanks, pipes, overhead poles and power lines, electrical transformers, and other structures shall also be identified. Surface features which are associated with underground or aboveground utilities shall also be identified, including but are not limited to, lights, manholes, handholes, inlets, etc.
MAA has established a SUE grid for BWI Marshall and Martin State Airports. The SUE grid is available by visiting AIRPortal > BWI > GIS Utilities >SUE Status or AIRportal > Martin State > GIS Utilities >SUE Status.
Unless approved in writing, SUE work shall be conducted at the grid level, meaning that SUE shall be completed for all utilities above and below ground in the entire grid and for every grid that the project touches.
The following information shall be provided in the consultant’s fee proposal as it relates to SUE:
A. A list or table of Grid IDs [(i.e. 33-30) – the unique identifier for the SUE grid(s)] that will be investigated. Grid IDs can be obtained by visiting AIRPortal > BWI > GIS Utilities >SUE Status or AIRportal > Martin State > GIS Utilities >SUE Status.
B. An image of the grids highlighting those that are included in the SUE investigation.
C. List of the consultant’s and/or subconsultant’s Engineer and GIS staff that will be involved with the SUE work. Qualification statements, resumes, and a QA/QC plan may be required for review and approval.
The consultant, MAA Project Manager, and GETS representative shall determine the appropriate quality level to be captured based on the last SUE survey performed, as well as, the type of work being performed within the affected grids. The consultant must involve an Engineer and a GIS Analyst in the project, regardless of the quality level being collected/submitted.
A. All SUE services shall be provided in accordance with applicable quality levels A through D of ASCE 38-02 Standard, latest edition.
B. Per ASCE 38-02 Standard, quality level designations A through D are cumulative, meaning that each quality level includes the activities performed for the quality levels below it in ranking. Levels are ranked from A (highest) to D (lowest). For example, if a project requires Quality Level C, the consultant must perform and deliver Quality Levels C and D.
C. Quality Levels are defined in its simplest form below. For full requirements refer to ASCE 38-02 Standard.
1. Level D – Records research
2. Level C – Identify ground surface features + Level D
3. Level B – Topographic survey + Levels C and D
4. Level A – Excavate and expose utility + Levels B, C, and D
D. If Quality Level A is required, the consultant is required to use minimally intrusive equipment such as vacuum excavation or hand excavation for test pits/test holes. Backhoe excavations are not permitted. Consultant must obtain an MAA Digging Authorization prior to any ground disturbance activities.
1.5.2 SUE Data Incorporating/Editing Process
Because SUE quality levels are cumulative, all SUE services will include Level D, records research. Using AIRPortal, the consultant may perform a review of all available drawings to identify existing utilities in the affected grid area(s). The BWI Projects Locator and MTN Projects Locator application in AIRPortal are also available to perform a spatial search for projects. Both Airports’ Projects Locator viewers only contain a partial number of the projects that have been completed at BWI Marshall and Martin State Airports and should not be solely relied upon to identify all projects in the grid area(s).
When data has been collected to the Level required in the scope of work, the consultant is required to assemble all utilities’ data and edit MAA’s existing GIS data via geodatabase checkout. A checkout must be requested from GETS using a Digital Data Request Form, available for download in AIRPortal.
Data shall be separated by utility type into the appropriate feature classes in accordance with MAA’s GIS Data Standards found in PEGS V1, Chapter 4 GIS Standards. The utility data shall be attributed with the following information:
A. Type of utility
B. Size
C. Material
D. Year built
E. Disposition
F. Data source
G. Quality level
H. Owner
I. Phase
J. Editor Name
K. Date of Last Update
Detailed information about each of the above listed attributes can be found in MAA’s Utility Data Editing Guidelines. GETS maintains and frequently updates the Data Utility Editing Guideline. GETS will provide the most current guideline with every geodatabase checkout.
Utilities found on drawings shown as abandoned shall be captured and attributed in the same manner as in-service utilities, but with a disposition of “abandoned”. Utilities are only deleted in cases of duplicate geometry; all other cases are handled by adjusting the disposition.
If a utility line exits the target grid(s), the consultant shall attempt to logically trace and connect the utility line to the existing utility feature in the adjacent grid. This could mean extending or adjusting the line to connect to the nearest physical feature (i.e. manhole, handhole, pole, etc.) if the utility records indicate a connection. In cases where the utility cannot be logically connected, the consultant shall place a notation in the description field to alert MAA GETS that there is a utility connecting into a feature of an adjacent grid.
Newly incorporated spatial data may not align exactly with the location of existing utility system features. When determining which geometry to use, the consultant must consider the quality level of the utility features in both the source and destination. The higher Quality Levels take precedence over the lower Quality Levels. Refer to PEGS V1, Chapter 1.5.1 SUE Quality Levels.
Attribute information identified during SUE projects may conflict with attribute information found in the existing utility system dataset. When that occurs, the consultant must determine which dataset contains more accurate information. The consultant shall consider the age of the data source and quality level in making the determination.
1.5.3 Electronic Deliverables for SUE
A. GIS Data
SUE data shall be submitted to MAA GETS in GIS format. The delivery of the GIS format shall be coordinated with GETS and delivered via a geodatabase checkout. Refer to PEGS V1, Chapter 4.6 MDOT MAA GIS Data Compliance Requirements.
The GIS deliverable must pass all ESRI Data Reviewer Quality Control Tests in accordance with PEGS V1, Chapter 4.8.1 Quality Assurance and Control of GIS Data, before being accepted. Tests will be provided by GETS to the consultant at the same time as the geodatabase checkout.
B. CAD Data – Refer to PEGS V1, Chapter 1.3.1 CAD Standards.
1.5.4 Data Exceptions
In cases where GIS features fail a Data Reviewer check but have a valid exception, the consultant will provide MAA with the file geodatabase used for the Data Reviewer session. This geodatabase shall have all corrected features removed from the reviewer table and only contain the exceptions. The consultant shall include a brief explanation for any feature exceptions.
1.5.5 Schedule
The consultant shall coordinate the schedule for delivery of SUE GIS data with their MAA Project Manager and GETS. All SUE work shall be initiated, completed, and delivered to MAA prior to the 30% submission of a task or in advance of the draft report submission, unless otherwise approved by the MDOT MAA Project Manager.