Appendix_8.7_Eglin_Design_Manual.pdf

February 2018

ENGINEERING DESIGN MANUAL

EGLIN AFB, FLORIDA

Table of Contents

Chapter 1 ‐ General Instructions 2

Chapter 2 ‐ Specifications 11

Chapter 3 ‐ Site Development 15

Chapter 4 ‐ Survey and Mapping 28

Chapter 5 ‐ Geotechnical 38

Chapter 6 ‐ Landscaping, Irrigation, Planting and Turfing 60

Chapter 7 ‐ Water, Wastewater and Environmental Protection 65

Chapter 8 ‐ Architecture 70

Chapter 9 ‐ Structural 84

Chapter 10 ‐ Plumbing 92

Chapter 11 ‐ Heating, Ventilating and Air Conditioning 97

Chapter 12 ‐ Fire Suppression System 104

Chapter 13 ‐ Other Mechanical Systems and Equipment 108

Chapter 14 ‐ Electrical and Electronic Systems 114

Chapter 15 ‐ Corrosion Control and Cathodic Protection Systems 132

Chapter 16 ‐ Telecommunications 147

Chapter 17 ‐ Cost Estimates 148

Chapter 18 ‐ Antiterrorism/Force Protection (AT/FP) 168

Appendix 174

Appendix 1 – Eglin Specific HVAC Requirements, Including DDC 175

Appendix 2 – Eglin Specific Fire Suppression Requirements 184

Appendix 3 – Eglin Specific Electrical / Electronic Requirements (Including Fire Alarms) 189

Appendix 4 – Eglin Specific Antiterrorism / Force Protection 216

Appendix 5 – Eglin Energy Conservation Requirements 223

Appendix 5 – Eglin Specific Termiticide Information 225

Chapter 1 ‐ General Instructions

1.1 GENERAL

1.1.1 Purpose

This Eglin Air Force base Design Manual prescribes standard procedures and instructions to accomplish the required design, drawings, specifications, project definition narrative, design analysis, cost estimates, and related support tasks for Military projects. This manual is written with the purpose of assisting designers with a consistent logical approach to performing design and developing design related documents. The organization of this manual is such that design procedures at various submittal stages are presented at the beginning of each Chapter with technical requirements presented last.

1.1.2 Statement of Work (SOW)

(a) The Statement of Work (SOW) will provide project specific execution criteria in conformance with the current version of this Eglin Air Force Base (AFB) Design Manual.

(b) A SOW will be issued to the A-E prior to conduct of the pre-design conference.

A-E attendance at the pre-design conference is considered essential in ensuring an understanding by the A-E of project, user, and installation requirements.

(c) As issued, the SOW will take precedence over the standard procedures and instructions in this manual. The A-E shall document any conflicts between this manual and the SOW in writing and bring them to the immediate attention of the Contracting Officer (CO).

(d) The A-E shall furnish sufficient technical, supervisory, and administrative personnel to insure satisfactory accomplishment of the work specified in the SOW, including accomplishment of work by agreed milestone dates and progress schedule. Additionally, the A-E shall furnish all services, materials, supplies, equipment, investigations, studies, and travel required in connection with the

SOW.

(e) The A-E shall accept directions only from the Contracting Officer (CO) or the

Contracting Officer’s Representative (COR). Requests or desires of the users or using agency made directly to the A-E shall be immediately brought to the CO’s attention. Any changes to the project scope or other provisions of the SOW must be authorized in writing by the CO.

(f) A-E Actions required prior to SOW approval.

(1) Updated progress chart. An updated progress chart shall be submitted with each payment estimate.

(2) The A-E shall use those individuals designated in their SF330 submission.

If any of these individuals are changed, the CO shall be notified in writing.

The SF330 shall be resubmitted with these personnel changes and those person’s individual qualifications. Government approval for these changes is required.

(3) Needs List. Throughout the life of the project, the A-E shall furnish a

“needs” list every two weeks until all open issues are resolved. The needs list shall also be included in each formal submittal. The needs list shall be an itemized list of design data required by the A-E to advance the design in a timely manner. This list will be maintained on a continuous basis with satisfied action items checked off and new action items added as required.

Action items in the needs list will include a sequence number, description of action item, name of individual or agency responsible for satisfying the action item, and remarks.

(4) Site investigations must be sufficiently thorough to ensure that design details are compatible with the project site. Siting shall not be changed without approval of Eglin AFB. At the Final Design submittal stage, the A-E shall make a plan-in-hand site visit to ensure that the final design accurately reflects existing site conditions. Any changes in site conditions that were made by the government during the design period shall be annotated and brought to the attention of the CO for direction.

(5) Should the project cost estimate exceed the funding limitation, the A-E shall make recommendations for reducing the project scope and/or identifying optional bid items of work. Upon receiving written approval from the CO, the A-E shall modify the contract drawings and specifications to incorporate all changes as necessary to reduce the base bid cost estimate below the funding limitation. If any criteria provided to the A-E during design prevents him from meeting the cost limitations, the A-E shall notify the CO immediately. The A-E shall list the specific criteria and explain the negative impact on the design cost.

(6) The A-E shall not correspond either in writing or verbally, with any prospective bidder during the advertisement period. All requests for information (RFI) from a prospective bidder shall be submitted in writing to the CO.

(7) During the construction period the A-E shall furnish advice as may be requested. During the construction period, limited construction phase services may be required. If construction phase services are required, appropriate modifications to the contract will be made.

1.1.3 Acronyms and Abbreviations

Acronyms and abbreviations are generally written out on first use in each chapter.

1.1.4 Discipline Coordination

(a) Individual design team members are responsible for coordinating their efforts with those of other design team disciplines.

(b) The A-E shall prepare a written record of each site visit, meeting, or conference, either telephonic or in person, and shall furnish this record within five working days to the CO with copies to all parties involved. The written record shall include the subject, the names of the participants, an outline discussion, and the recommendations or conclusions reached.

1.2 APPLICABLE PUBLICATIONS

Applicable publications are listed in various chapters of this manual. The most recent editions of the cited publications at the start of Concept Design (30%-35%) for D-B-B or Interim Design (50%) for D-B will be referenced and incorporated (as appropriate) in work prescribed by this manual. The publications cited in individual chapters, but referred to thereafter by basic designation only, form a part of this manual. The publications are supplemented by the Unified Facilities Guide Specifications (UFGS) to form design criteria. Unless specifically stated otherwise in this manual or the SOW, the designer shall be responsible for obtaining all publications applicable to the design of the project including, but not limited to, the cited publications. The recommended source for many publications is the Whole Building Design Guide (WBDG) which contains USACE technical Manuals (TM), Unified Facilities Criteria (UFC), Engineering Regulations (ER), Engineering Technical Letters (ETL), and industry and other government standards. The WBDG is at the following web site:

http://www.wbdg.org

For A-E projects, additional project specific customer and user requirements, or additional publications and references may be listed in the SOW. The A-E shall furnish copies of all instructions, manuals, and other documents pertaining to design requirements to all consultants to insure a completely coordinated design.

1.3 INSTRUCTIONS

1.3.1 Pre-Design Conference

The CO shall request that the designers attend a pre-design conference at the project site and participate in discussions prior to the preparation of a fee proposal and negotiations for a project designed by an A-E.

During these discussions, all aspects of the required effort, which shall affect the designer’s effort, will be addressed.

(a) A-E Design. The A-E will be responsible for recording minutes from the pre-design conference. The A-E designer shall be furnished a draft SOW which will contain project specific design criteria and instructions. Subsequent to the pre-design conference, the A-E designer shall receive a request to furnish a fee proposal for accomplishing the work agreed upon during the conference.

1.3.2 Quality Management

An A-E Quality Assurance Plan (QAP) is required for all projects.

1.3.3 Studies and Renderings

(a) Studies. At various times, studies may be required that do not conveniently fit into the design phases and procedures required in this Manual. In such cases, requirements will be detailed into the SOW.

(b) Interior/exterior color renderings necessary for a visual presentation to the customer shall be furnished only as determined during the pre-design meeting, funded, and as directed in the SOW for A-E projects.

(1) Renderings. The style of rendering and number of views required will be determined at the pre-design conference. Final rendering size(s), matting, framing and glazing will also be established at that conference. Each framed rendering will include: project name, project location, U.S. Air Force, Eglin Air Force Base, and the A-E firm name. The number and size of unframed photographs of the rendering(s) will also be determined at the pre-design conference. These requirements will be incorporated into the final SOW issued to the A-E.

1.3.4 Charrette

Charrette conduct will be determined during the pre-design conference. The requirements will be specified in the SOW.

1.3.5 Life, Health, and Safety Standards

The most recent version of the International Building Code (IBC) will be used as the basis of design of facilities unless specifically exempted by the customer and documented. In addition, the most recent version of NFPA 101 Life Safety Code and other NFPA Codes shall be incorporated into the design as appropriate.

UFC 1-200-01 will be used by all designers as the basis of determination of code requirements (changes mandated in use of codes in UFC 1-200-01 will be adjusted based on the use of the most recent IBC and NFPA codes until UFC 1-200-01 is updated). The facilities, systems, and equipment design standards of the Occupational Safety and Health Act, Code of Federal Regulations, Title 29, Chapter XVII, Parts 1910 and 1926, as applicable, shall be incorporated by the designer into all design and analyses. Other customer-specific health and safety regulations will be determined during the pre-design conference, and incorporated in the design effort. Any problem in incorporating these standards due to conflicts with other technical criteria shall be promptly submitted to the CO for resolution.

1.3.6 Design for the Physically Handicapped

Unless specifically stated otherwise in the SOW, all facilities shall be designed to be accessible to and usable by handicapped persons in accordance with the American Disabilities Act (ADA) Accessibility Guidelines (ADAAG) and the Uniform Federal Accessibility Standards (UFAS). Consolidated ADA – Architectural Barriers Act (ADA-ABA) guidelines were published in 2004 but have not been adopted by Eglin.

1.3.7 Topographic Surveys, Easements, and Utilities

Unless otherwise specified during the pre-design conference, topographic, hydrographic, and utility surveying and mapping data will be funded and obtained. Chapter 4 SURVEYING AND MAPPING provides specific instructions. Specific requirements for A-E designs will be included in the SOW.

Subsurface utility investigation using Ground Penetrating Radar (GPR) or other means of determining the three dimensional location of underground utility lines will be specifically addressed in the SOW.

1.3.8 Foundation Investigation

Unless otherwise determined during the pre-design conference, foundation investigations shall be completed and funded (including soil and rock borings, sampling, laboratory testing, and pile load tests, where applicable), as well as test such as percolation tests for septic tanks, soil resistivity tests for grounding and cathodic protection systems and infiltrometer test for storm water detention ponds. Chapter 5 GEOTECHNICAL provides specific instructions. Specific requirements for A-E designs will be included in the SOW.

1.3.9 Environmental Regulatory Permits

Responsibilities for environmental permits include:

(a) The designer shall contact the appropriate Federal, State, local, and interstate pollution and environmental control agencies to determine the permits required and procedures and documentation necessary to obtain them. A written record of each such contact shall be prepared and furnished within five working days to the CO with copies to all parties involved.

(b) Where formal documents are required to be submitted to obtain permits, the designer shall prepare all such documents and provide them in a “ready-for-signature” condition. This includes necessary copies of the plans, specifications, design analysis, and other required supporting documents. After review by Eglin Environmental and comment incorporation, the corrected documents will be signed by the appropriate official and submitted to the appropriate agency. Permit requirements shall be ascertained and documented by the designer during the Concept Design stage.

(c) The designer shall provide the following information and data for each required permit with the Concept Submittal:

(1) Permitting Authority (State, local, etc.)

(2) Type of permit required (construction, operation, etc.)

(3) Procedure and time necessary to complete the permit application.

(4) Fees required.

(5) Statement that the project is covered by variances or that permits are not required. If a variance is required, the procedures for obtaining the variance shall be provided. If a permit is not required, reasons and supporting justification (i.e. cite state, local, and/or other regulations) shall be furnished.

(6) An evaluation of all State and/or local regulations to determine if monitoring devices are needed. Where required, monitoring devices shall be included in the project design.

(d) The designer shall provide the completed permit applications not later than the

Interim submittal or 60 days prior to the Final submittal, whichever is earliest.

Permit applications shall be ready for signature by the appropriate official and submission to the approving authority.

(e) With the Final submittal, the designer shall provide supporting documents, plans, and specifications. The designer shall also have accomplished the necessary coordination to obtain permit application approvals.

1.3.10 Sustainable Design

Sustainable Design is an integrated approach to planning, designing, building, operating and maintaining facilities in a collaborative and holistic manner among all stakeholders. It is meant to provide resource efficient, environmentally friendly and healthy facilities with emphasis on renewable energy and recycled materials. The project specific criteria and rating level will be determined during the pre-design conference.

The SOW will identify requirements for A-E projects.

1.3.11 Anti-Terrorism/Force Protection

Anti-Terrorism/Force Protection is an inherent part of all projects. See Chapter 18 ANTI- TERRORISM/FORCE PROTECTION for specific requirements.

1.4 DEFINITIONS

1.4.1 Design Analysis

(a) The design analysis shall be provided with each submittal including Ready-To- Advertise (RTA) (unless it is determined during the pre-design conference that it is not required at a specific design submittal phase).

(b) At RTA, the design analysis is not a contract document, but rather a final documentation of the basis of design for the AF Project Manager (PM), and digital archival document for Eglin CE. The design analysis shall be developed from Concept Design to include a discussion of any new or unfamiliar products, critical product features, critical milestones that may require designer consultation, items of particular customer interest revealed in design meetings, shop drawings of particular interest or criticality, anticipated difficult construction features.

(c) The design analysis is a written explanation of the project design and is expanded and revised for each sub mission. The design analysis shall contain a summary of the criteria for and the history of the project design, including criteria designated by the customer, letters, codes, references, conference minutes, and pertinent research. The justification for each major selection and design decision shall be clearly stated. Design calculations, computerized and manual, shall be included in the design analysis in digital format. Narrative descriptions of design solutions shall also be included. Diagrams and sketches to convey design concepts may be provided to illustrate all written material. Design phase review comments and the specific actions (annotations) taken in response to each comment from the preceding design phase review shall be included with each submission of the design analysis. Specific requirements for the design analysis are provided in other chapters of this manual.

1.4.2 Drawings

Drawings are required in each design submittal. The drawings at each submittal stage shall be complete, thoroughly checked, and coordinated. Specific drawing requirements are defined below and in other chapter of this manual.

1.4.3 Specifications

The Uniform Facilities Guide Specifications (UFGS) 48 Division format is mandatory. The specifications shall be developed in accordance with guidance provided below and in other chapters in this manual.

1.5 SUBMITTAL REQUIREMENTS

1.5.1 General

Requirements for each submittal are general described below. Additional requirements are contained in other chapters of this manual. Specific instruction for A-E design projects for number of copies, addressing, and other instructions are provided in SOW. Covers for all submittals shall be white with black letterings (Colored covers on plans and spec books are reserved for advertised solicitations only). Submittals shall not include the solicitation number on the drawings, specs or covers (solicitation numbers on plans and spec books are reserved for advertised solicitations only).

1.5.2 Project Definition (10-15%)

This submittal represents approximately 10 to 15% of the design effort and shall be used to document and validate project requirements and the construction costs. The submittal shall include preliminary schematic plans, a narrative describing each aspect of the project including a parametric cost estimate. This level of design effort equates to the final report prepared to document charrette completion.

1.5.3 Concept Design (30-35%)

This submittal represents approximately 30-35% of the design effort and shall be of sufficient detail to show how the user’s functional and technical requirements will be met, indicate the designers approach to the solution of the technical problems, show compliance with design criteria or provide justification of non-compliance, and provide a valid estimate of cost. The Concept Design consists of:

(a) Design Analysis:

(1) Design narrative, notes, and design calculations for all disciplines.

(2) Intended (outline) specification list.

(3) Environmental permitting memorandums.

(b) Concept drawings.

(c) Bidding schedule with Bid Options identified when applicable.

(d) Concept cost estimate.

(e) Required information and data for each required permit.

(f) Annotated project definition review comments.

1.5.4 Value Engineering

(a) Shortly after or in conjunction with the Concept Design submittal, the designer shall perform a Value Engineering (VE) Study as directed. It is strongly recommended that the VE study be conducted at the installation, and involve user and base representatives.

(b) VE Study. This effort shall include study of design memorandum documents, cost data, and other information furnished as the basis of design. The VE study shall develop alternate designs to achieve the required mission(s) or function(s) at the lowest overall cost consistent with performance for structures, structure or facility siting, site development, equipment, electrical and materials or methods. The study includes examination of high cost items including life cycle cost, anticipated construction time, and conservation of energy. Design details and analyses will be considered and alternatives developed as appropriate. The VE team should consider the latest technology in the development of alternatives to achieve maximum results for life cycle costs, energy conservation, functional use, maintainability, and first cost (construction) savings.

(c) The VE Team. The VE Team shall be headed by an architect with no prior input/knowledge of the design. Other disciplines required for participation are civil, structural, mechanical, electrical, and cost engineering. Similarly, VE team members shall have no prior input to, or knowledge of the design. Selected team members will be different from the design team. All members should have past experience performing VE analysis.

(d) VE Report. The results of the study shall be prepared and submitted on 8-1/2”x11” bond paper. Back-up data and detailed estimates shall be included. Sketches may be 8-1/2”x11” or 11” x 17” fold-outs. Pages must be sequentially numbered in the lower right-hand corner for assembly purposes. Report will include as a minimum:

(1) Transmittal Letter.

(2) Cover sheet.

(3) Table of Contents

(4) Summary of existing and proposed design.

(5) Study methodology.

(6) Tabulation of proposed changes with first cost savings, operations and maintenance costs, and energy savings displayed separately. Life-cycle cost analysis shall be included. Present worth and annualized cost shall be computed using ten percent annum.

(7) Advantages and disadvantages of proposed changes.

(8) Appropriate drawings for each proposed change showing the existing conditions and proposed alternatives.

(9) Cost estimates comparing the existing design with all proposed changes.

(10) Results and conclusions.

(11) Recommendations shall include comments concerning the feasibility of implementation of each proposal. A separate summary tabulation will be included in the front of the report indicating if the change is minor or major with recommendations concerning the most efficient way to accomplish each stage.

(12) List of possible design conflicts.

(13) Summary of VE actions.

(e) VE Report Distribution. The report summarizing the VE proposals must be submitted to those listed in the SOW Design Submittal Distribution List.

(f) Implementation of Approved VE Changes. VE proposals accepted by Eglin shall be incorporated into the subsequent submittals of the design project. The designers are required to validate savings and accepted proposals for their final impact on the project cost estimate.

(g) The VE proposals and ideas become the property of the Government and may be used on future contracts or designs without additional compensation to the A-E.

1.5.5 Interim Design (50-60%)

This submittal, if required, is intended to insure that funding limitations are not being exceeded and that the drawings, design analysis, specifications, and cost estimate are proceeding in a timely manner and that the design criteria and previous review comments are being correctly interpreted. Redlined, marked-up specifications shall be submitted at this design phase. The Interim Design shall consist of;

(a) Design Analysis developed to approximately 60% completion including Bid Options where applicable.

(b) Approximately 60% complete drawings including those addressing construction phasing.

(c) Detailed cost estimate developed to approximately 60% completion including Bid Options where applicable.

(d) Redlined, marked-up specifications.

(e) Annotated Concept review comments.

(f) Completed permit applications (if an Interim submittal was not required, the completed permit applications are required 60 days prior to the Final submittal).

1.5.6 Final Design (Unreviewed 100%)

This submittal represents a 100% complete design with the exception of the incorporation of any review comments resulting from the review of the submittal. The Final design shall consist of;

(a) Design Analysis with all items 100% complete. It shall include all back-up material previously submitted and revised as necessary, all design calculations, all explanatory material giving the design rationale for any design decisions which would not be obvious to an engineer reviewing the Final drawings and specifications.

(b) 100% complete drawings including those addressing project construction phasing.

(c) Specifications. Redlined, marked-up specifications if an Interim submittal was not made. Final edited specifications if an Interim submittal was made.

(d) Bid Schedule and Explanation of Bid Items. Identify Bid Options where applicable.

(e) Detailed 100% complete cost estimate.

(f) Annotated Interim review comments.

(g) All supporting documentation required for permit application approvals.

1.5.7 Ready-To-Advertise (RTA) (Reviewed 100%)

This submittal represents a complete design (design analysis, specifications, and drawings) including annotated design submittal review comments that answer and/or incorporate review comments resulting from the review of the Final design submittal.

Chapter 2 ‐ Specifications

2.1 GENERAL

2.1.1 Purpose

This chapter provides guidance for the preparation of contract specifications. Architect-Engineer (A-E) designers shall use the Unified Facilities Guide Specifications (UFGS) on all projects unless specifically directed otherwise.

2.1.2 Automated Specifications

(a) The Unified Facilities Guide Specifications (UFGS) in the Construction Specification Institute (CSI), Masterformat 2004 numbering system shall be used.

These specifications consist of a total of 48 divisions versus the old numbering system of 16 divisions.

(b) The designer shall not mismatch or combine the old 16 division specifications with the new 48 division system. Any such combining of the two systems will not be accepted and will be returned to the designer for a complete resubmittal of the project specifications.

(c) It is highly recommended designers use SpecsIntact software as its automated specification system. This software is available for free on several sites on the internet. The following internet addresses contain necessary software, help manuals, and Unified Facilities Guide Specifications (UFGS):

SpecsIntact Software Support Unit Home Page http://specsintact.ksc.nasa.gov/

Whole Building Design Guide Home Page http://www.wbdg.org

(d) Upon accessing the Whole Building Design Guide (WBDG) website, a list containing UFGS guide specification will be shown. These lists provide a divisional breakdown for the guide specifications. In order to retrieve the required guide specification, click on the Division in which the specification is located (i.e., Division 2; Section 02 41 00 – Demolition). Specifications downloaded from the WBDG site page are in a compressed (zipped) format as well as Adobe .pdf format.

In order to manipulate and use these files, you must “unzip” them prior to opening the file for use.

2.1.3 Scope

The designer is responsible for the accurate preparation and coordination of the technical specifications.

2.1.4 Quality of Work

Specifications prepared by the designer shall be accurate, clear, and precise and should not be subject to interpretation. The specifications shall be specific, free of ambiguities, and well coordinated with the drawings. The designer shall be solely responsible for insuring the relevancy and accuracy of cross-references between technical sections of the specifications.

2.2 OUTLINE SPECIFICATIONS

The designer shall submit a list of specifications with the Concept design analysis submittal. The list of specifications will support the various types of construction intended and described in the design analysis, and provide a description of any specifications which must be developed for the project.

2.3 TECHNICAL SPECIFICATIONS

2.3.1 Generating Original Specifications

(a) Designer developed specifications may only be used when UFGS specifications are not available. The original specifications must match the UFGS specifications in format and document arrangement. Designer developed specifications shall be prepared in accordance with UFC 1-300-02, Unified Facilities Guide Specifications (UFGS) Format Standard using SPECSINTACT (SI), the automated system for preparing standardized facility construction specifications.

UFC 1-300-02 requires that each UFGS carry an identifying document section number in accordance with the Construction Specifications Institute (CSI) MasterFormat (MF). The UFGS specification utilize a 14 character designation of

MF 2004 section numbers in the format: “NN NN NN.NN NN”, where N’s are numbers. CSI has named, numbered or otherwise reserved to the 4th level. The SI steering committee has agreed that the 5th level double digit designator would replace the former suffixes used to denote sections that are not currently unified:

“A” or “10” for Army, “N” or “20” for Navy, “S” or “40” for NASA. An example of the five level numbering system agreed for the UFGS is as follows:

Level 1 – 31 00 00 Earthwork Level 2 – 31 41 00 Shoring Level 3 – 31 41 16 Sheet Piling Level 4 – 31 41 16.11 o For activity or project specific use o For multiple contracts or alternate systems o For very unique narrow scope UFGS (minimal)

Level 5 – 31 41 16.11 10 Designation for non-unified sections o 10 Army o 20 Navy o 30 Air Force o 40 NASA o 50 – 90 other Future participating agencies

(b) “Functional or descriptive specifications” are normally prepared using industry standards, manufacturer’s data, and other available information. These specifications shall be developed by listing parameters, methods, techniques, salient features and other requirements that several manufacturers can satisfy.

These specifications shall list the essential features, requirements, minimum functions, and other factors to clearly indicate the type and quality of item(s) required. Specifications shall not be developed around a single manufacturer.

(c) Sole Source Specifications:

Sole source specifications are to be avoided. The use of trade names and proprietary items and the drafting of a specification by adopting a manufacturer’s description of a particular article or procedure shall be avoided. There may be instances, however, when only one manufacturer’s will satisfy the job conditions.

For example, in rehabilitation work, updating a particular piece of mechanical equipment may require new parts from the manufacturer of that particular piece of equipment. In this case, specifying the “Brand” or “manufacturer’s” name would be acceptable provided that “Sole Source Approval” is received from higher authority.

(d) “Or Approved Equal” Specifications:

Experience indicates that a “trade name or approved equal” description is appropriate only as a last resort and should be used with great care and discretion.

When this approach is used, the contract provisions will include those salient features of the item specified upon which equality will be determined.

2.3.2 Tailoring and Coordinating of Specifications

(a) Each specification used in the preparation of project specifications shall be tailored to fit the requirements of the project. Where numbers, symbols, words, phrases, clauses, or sentences are enclosed in brackets [ ], a designer’s choice or modification must be made. The designer shall exercise care in making the choice or modification to be made. Where blank spaces are provided for insertion of data or text, the designer shall insert the appropriate data or text. Where entire paragraphs are not applicable, they must be deleted. Paragraphs describing systems or materials not used in the construction of the project shall be deleted. When necessary to add requirements, they must be consistent with the other requirements of the specification and must not unnecessarily restrict products that can be furnished. Prior to marking up each specification for the Interim (if this submittal is required) and Final design submittal, the designer shall review all notes attached at the beginning of the specifications. Prior to submitting the Ready To Advertise (RTA) specifications, the designer must execute the bracket verification tool if using SpecsIntact software. A complete error free report will be required before submission of the RTA specifications.

(b) Each specification used in the preparation of project specifications shall be coordinated with other specification sections included in the project and with the project drawings. Duplication of requirements in other sections or on the drawings should be avoided. Cross-referencing of requirements will be done only when necessary to avoid misunderstanding. If the specification states “as shown” or similar wording, the requirement must be shown on the drawings. If the drawings reference the specifications, the specifications must cover the reference. If a specification references another specification, the referenced specification must be included in the project. Prior to submitting the Ready To Advertise (RTA) specifications, the designer must execute the section verification tool within the SpecsIntact software. A complete error free report will be required before submission of the RTA specifications. The designer shall insure that specifications and drawings are properly used; specifications to establish requirements such as quality and workmanship, and drawings to establish requirements such as layouts and dimensions.

2.3.3 Tailoring Specification Shop Drawing Submittals

(a) The shop drawings typically listed in each UFGS specification are intended to cover the majority of circumstances for a variety of projects. Not all shop drawings listed in the specification need to be included in every project. During the editing of the Shop Drawing Submittal portion of each specification, the designer should carefully consider which Shop Drawing Submittals are actually required from an Engineering Verification and Quality Control perspective. All submittals that are not absolutely necessary should be deleted whether listed for “Government Approval” or “For Information Only”.

(b) Submittals Requiring Government Approval. Shop drawings and product data submittals requiring government approval, should be limited to major pieces of equipment or systems requiring review by the designer, color selection, testing reports, etc. For each submittal that requires Government Approval, provide the desired reviewer designation “CD” for “Construction Division”, “ED” for “Engineering Division”. “ED” should be used for all submittals that are an extension of the design.

2.4 SPECIFICATION SUBMITTALS

2.4.1 Interim Submittal Specifications

If this submittal is prepared, redlined, marked-up specifications will be provided to allow reviewers to evaluate choices made by the designers. The Statement of Work (SOW) shall identify the recipients of the hardcopies.

2.4.2 100% Unreviewed Submittal Specifications

(a) If an interim submittal is not made, 100% Unreviewed Final Submittal specifications will be provided in redlined, marked-up format in hardcopy. If an Interim submittal is made, the designer shall submit full edited specifications at the 100% Unreviewed Final Submittal Design review stage in hardcopy.

(b) Boiler Plate (Front-end contract clauses) will be furnished by the government to the A-E for inclusion in the 100% Unreviewed Final Submittal.

2.4.3 Ready-To-Advertise (RTA) Submittal Specification

Following the 100% Unreviewed Final Submittal review, review comments will be provided to the designer. The designer shall incorporate the comments into the specifications and prepare the final specification.

Chapter 3 ‐ Site Development

3.1 GENERAL

3.1.1 SCOPE

This chapter states the criteria, requirements and guidance for civil engineering design. The design shall be accomplished in accordance with appropriate technical publication documents and the basic requirements furnished in the project Statement of Work (SOW).

3.1.2 QUALITY OF DESIGN

It is the purpose of Eglin Air Force Base to obtain excellent siting and civil design resulting in efficient, economical and effective long term paving, grading and drainage conditions.

3.2 APPLICABLE PUBLICATIONS

UFC Unified Facilities Criteria (UFC) including UFC Series 3-200:

Civil/Geotechnical/Landscape Architecture shall be utilized to provide planning, design, construction, sustainment, restoration, and modernization for Department of Defense (DoD) Projects.

AASHTO A Policy on Geometric Design of Highways and Streets, American

Association of Highway Transportation Officials (AASHTO).

USDOT Manual of Uniform Traffic Control Devices (MUTCD) for Streets and

Highways, United States Department of Transportation.

NPDES State specific requirements documents and publications for National Pollutant Discharge Elimination System (NPDES) construction permits and best management plans.

3.3 PROJECT DEFINITION (10-15% Design)

The designer shall develop a narrative and conceptual site plan which describe and present the conceptual site features based on the project requirements. The narrative shall discuss siting requirements and site concerns including wetlands, Installation Restoration Program (IRP) sites, and soil and groundwater contamination. The conceptual site plan should be an efficient layout with emphasis given to user requirements. The conceptual site plan shall show building locations, parking areas, roads, limits of paving and hardstands, conceptual storm water management device locations, and pedestrian access points. The plan shall be developed to a point such that a preliminary cost estimate may be prepared.

3.4 CONCEPT DESIGN REQUIREMENTS (30-35% Design)

3.4.1 Concept Design Analysis

Provide information regarding the following as applicable:

3.4.1.1 General

(a) General overview of major site features planned, such as building orientation, drainage patterns, parking provisions, traffic circulation, provisions for the handicapped, security requirements, airfield pavements work, etc.

(b) Provide a description of the location of any wetlands, as defined by Federal and/or

State criteria, historically significant areas, and areas with potential endangered species of wildlife within the project area. Describe and define IRP sites. All areas shall be defined by qualified professionals and flagged in the field. The project topographic survey shall label and present the defined areas. Geometric coordinates shall be clearly shown on the design drawings for all environmental areas such as an IRP site or wetland boundaries.

(c) Provide applicable State/Local flood requirements.

(d) Discuss existing site features including general topography, acreage, boundaries, adjacent site usage, etc.

(e) Impacts of new construction on existing facilities. For projects with critical phasing requirements, such as airfields or projects with major impacts to existing facilities, present a preliminary phasing discussion. This preliminary phasing plan shall also be presented in plan form and shall fully discuss anticipated lengths of construction, alternate phasing schemes, and project cost impacts.

3.4.1.2 Removals

(a) Provide preliminary discussion of any items requiring removal or relocation.

(b) Discuss the methods and location of the disposition of waste or salvage materials.

3.4.1.3 Geometry

(a) Provide rationale for siting of major site elements.

(b) Airfields: Provide list of specific clearances based on airfield criteria and list manual(s) for all portions of the new work.

(c) Work other than Airfields: Provide setback requirements or specific clearance requirements for major features of work such as buildings, parking areas from streets, hardstands, etc.

3.4.1.4 Storm Drainage

(a) Provide a summary of specific Federal, State, and/or Local storm water permit requirements for water quality/quantity for the project including fees for permit applications and the name of the agency to which the permit application check will be written. Discuss the impacts on the site design. If no storm water permits or requirements are required, provide a statement to that effect. Provide documentation from the appropriate regulatory agency and regulators name if applicable.

(b) Discuss the preliminary storm water design scheme and discuss impacts on the existing storm drainage system.

(c) Provide selected design values to be used in the storm drainage calculations such as runoff coefficient, infiltration rate and rainfall intensity. Rainfall intensity shall be based on the most stringent of regulatory requirements. If no regulatory design storm exists, rainfall intensity shall be based on the 25-year frequency, critical duration rainfall event. Post-construction storm water runoff shall not exceed the calculated pre-construction runoff rate. Storm water quality must be addressed by treating the first one inch (1”) volume of storm water runoff.

(d) Provide preliminary sizes and location of storm drain pipes and collection/discharge devices.

(e) Provide preliminary size and preliminary calculations for the required storm water treatment/storage ponds. Discuss impacts on the project site.

(f) Provide preliminary Pre and Post construction discharge values for the applicable storm event.

(g) Discuss the proposed storm drain pipe materials.

3.4.1.5 Grading

(a) Discuss existing site features affecting grading such as buildings, streets, curbs, walks, fences, water courses, ponds, elevation of high ground water, rock outcrops, etc.

(b) Provide minimum elevation to provide flood protection (if applicable)

(c) Planned finished floor elevation (F.F.E.). Planned building shall not be inundated by flood waters created during the 100-year frequency storm event.

(d) Cut and Fill requirements and rough estimate quantities.

(e) Discuss minimum and maximum slopes to be used in the design for embankments, ditches, pipes, etc. Unless structural stabilization is provide, maximum slopes for pervious surfaces is 3 horizontal:1 vertical.

3.4.1.6 Pavement Structure Design

(a) Vehicular Pavements Thickness Design.

i. Provide specific design values for which pavement thickness is based including number, type, and maximum weights of vehicles, category of traffic, class road or street, and resulting design index.

ii. Flexible Pavements – Flexible pavements shall be designed in accordance with the current version of the Florida Department of Transportation (FDOT) Flexible Pavement Design Manual.

iii. Rigid Pavement – Rigid Pavements shall be designed in accordance with the current version of the FDOT Rigid Pavement Design Manual.

(b) Discuss the proposed base course type and select sub grades. Provide intended compaction requirements. All non-airfield pavements shall be designed in accordance with Florida Department of Transportation Design requirements.

3.4.1.7 Roads and Streets, and Parking Areas

(a) Provide AASHTO design vehicle for which turning movements are to be provided for and corresponding minimum turning radius.

(b) Provide project design speed.

(c) Provide minimum degree of curvature and control grades per FDOT standards.

(d) Provide applicable site and stopping distance requirements per FDOT standards.

(e) Provide lane and shoulder widths per FDOT standards.

(f) Provide cross-slopes for lanes and shoulders per FDOT standards.

(g) Provide embankment slopes.

(h) All flexible pavements shall be edged with either a minimum 12”h x 8”d concrete ribbon curb or curb and gutter with 6” tall curb and 18” wide gutter. Curbing for rigid pavements shall be as required for storm water management.

(i) Provide requirements for sidewalks, guardrails, traffic signs and markings, fencing, etc.

(j) Provide traffic control devices in accordance with the latest issue of the Manual on Uniform Traffic Control Devices (MUTCD)

3.4.1.8 Parking and Open Storage Areas

(a) Discuss the types of vehicles to be accommodated.

(b) Discuss means of determining the required number of parking spaces.

(c) Parking stalls shall be 9’ wide x 18’ long.

(d) Discuss the number, size and location of required handicapped parking stalls and associated accessible routes to buildings being served. Parking spaces shall be designed in accordance with the current ADA Standards for Accessible Design.

(e) Provide general location of storage areas.

(f) Provide location(s) of ingress/egress.

(g) Provide pedestrian access to facility being served and within the parking area.

(h) Use of 90°, 60°, or 45° parking is permitted.

3.4.1.9 Miscellaneous Site Features

(a) Sidewalks – width and location. Sidewalk width shall take into consideration, overhang from adjacent vehicles.

(b) Fencing – justification, type, size and location of vehicular and pedestrian gates.

(c) Dumpster Locations – quantity of dumpsters, location, screening.

3.4.1.10 National Pollutant Discharge Elimination System (NPDES) Construction Permit.

Provide specific requirements for State and/or Federal NPDES construction permit for the project. If the project is exempt, state so.

3.4.1.11 Erosion and Sediment Control Plan

Describe the intended plan for the design of sediment and erosion control for the project.

The project design engineer’s responsibility for the development of the Erosion and Sediment Control plan is to provide general guidelines only and to serve as a basis in obtaining an NPDES permit. The ultimate responsibility for developing and implementing the Erosion and Sediment Control plan is the construction General Contractor’s (GC). The GC shall modify and update his plan to coincide with construction schedule and activities.

3.4.1.12 Outline Specifications

Provide a list of all Unified Facilities Guide Specifications that the designer intends to prepare to use for the project.

3.4.2 Concept Drawings

The following are typical construction drawing sheets. This is a guide only. These sheets may not all be applicable to the project and may be omitted. Additional sheets may also be added if appropriate.

Title Sheet and Index Project Location and Vicinity Maps Project Symbols, Legends and Abbreviations Sheet

General Site Overview Plan Geometric Layout Plan Grading and Storm Drain Plan Demolition and Removal Plan Centerline Profile Sheets Typical Sections Sheet Composite Utility Plan Existing Site Topography Survey and Utilities Plan Special Project Phasing Requirements

3.4.2.1 Title Sheet and Index

(a) Provide Project Title

(b) Plan Sheet Index

3.4.2.2 Location and Vicinity Map

(a) Indicate project site. Provide preliminary borrow and spoil areas, haul routes, and contractor’s access to the site.

(b) Provide State Vicinity Map

(c) Provide Location Map for local access to the site.

3.4.2.3 Project Symbols, Legends and Abbreviations Sheet

(a) Provide graphic symbols legends (see Tri-Service Standards)

(b) Provide preliminary list of abbreviations used in plan assembly.

3.4.2.4 Provide General Site Overview Plan

(a) Show the overall site plan of planned work (scale may be determined by the designer to best fit project requirements).

(b) Annotate major items of work, significant removals, and/or phasing.

(c) Site topography with major existing features, buildings, and/or roads shall be presented with the new work.

3.4.2.5 Geometric Layout Plan

(a) Provide an overall site plan showing total development.

(b) Show the proposed geometry of the site plan using a minimum scale of 1” = 30’ unless otherwise approved by the Contracting Officer.

(c) Use graphic symbols and/or line work to distinguish between new and existing site work.

(d) Provide sufficient geometric information to adequately locate all new major site elements.

(e) Identify the coordinate system used. Include a North arrow.

(f) Provide centerline stationing for all roads, streets, parking areas, runways, taxiways, etc.

3.4.2.6 Grading and Storm Drainage Plan

(a) Show the complete drainage concept using finished contours and slope arrows where applicable.

(b) Use a minimum scale of 1” = 30’ unless otherwise approved.

(c) Show and identify all existing buildings and facilities on plan.

(d) Show the proposed finished floor elevation and critical spot elevations.

(e) Provide control monument data, and list vertical and horizontal data for each.

(f) Reflect existing utilities with the topography. If necessary for clarity, show removals, relocations, and new work for utilities on separate plans.

(g) All contour intervals shall be 1-foot.

3.4.2.7 Demolition and Removal Plan

(a) Indicate items to be demolished and/or removed.

(b) Pavement structures: Indicate pavement layer thickness for removal depths if information is available.

(c) Drawing scale shall match the geometric layout and grading plans scales.

3.4.2.8 Centerline Profile

(a) Roads and Streets: Provide preliminary centerline profile. Show existing ground line and preliminary new finish grade with percent new grades and vertical curve data indicated.

3.4.2.9 Typical Sections (New Work) for Roadways and Parking areas

(a) Roadways: Provide preliminary typical sections presenting ach different roadway type or width. Indicate lane widths, shoulder widths, curb and gutter, and cross-slope.

(b) Parking Areas: Provide preliminary typical pavement sections for various parking areas.

3.4.2.10 Composite Utility Plan

Present the new and existing site features with all utilities underground and overhead shown.

3.4.2.11 Existing Site Topographical Survey and Utilities Plan

Present the site topographical survey.

3.4.2.12 Project Construction Phasing Plan

Present the preliminary project phasing requirements.