Scope of Work.pdf

12 DEC 2019

DESIGN-BUILD CONTRACT APPENDIX A

PROJECT DESCRIPTION AND SCOPE OF WORK

PROJECT NAME: Big Creek Road Stabilization and Repair Design-Build Project

LOCATION: Big Creek Boat Dock Road, Big South Fork National River and Recreation Area, McCreary County, KY

P2#: 483856

1. GUIDANCE, REFERENCES, PRECEDENCE

1.1. The Task Order for which this Scope of Work (SOW) applies will be issued under Hubzone MATOC W912QR-

14-R-0036 (to one Design-Build contractor under contracts W912QR-15-D-0019 through 0023). The base contract will remain active until project design and construction is complete and accepted. Provisions of the MATOC Contract are applicable to this Task Order unless otherwise indicated in this SOW. This SOW and attached or referenced exhibits provide specific instructions for the design and construction of this project and, in the case of conflicts, take precedence over the requirements of the MATOC.

1.2. The Contractor shall provide Architect-Engineer (A-E) engineering and design services (design) and full, turnkey construction services in accordance with generally accepted and currently recognized engineering, design, and construction practices, procedures, and principles. The A-E shall serve as the Designer of Record (DOR) for this project. The DOR shall provide the design following U.S. Army Corps of Engineers (USACE) Engineering Regulation (ER) 1110-2-1150 and other USACE Engineering Regulations and Circulars (to be considered minimum standards for design and construction quality), National Park Service (NPS) design criteria, and State of Kentucky Transportation Cabinet (KYTC) design criteria and standards, as well as pertinent USACE and OSHA safety and operations criteria. The use of UFC and/or

USACE Nashville District (LRN) specifications is required.

Contractor services shall consist of the preparation of contract plans and technical specifications for the design of and all construction activities to complete a roadway repair and bank stabilization project – accounting for base, shoulder, geotechnical, cross section slope, stormwater system, signage, associated traffic control, utilities (including a regional water line and overhead high voltage power lines), signage, traffic safety, etc. typical for a rural gravel haul road – of a limited access passenger vehicle and haul truck gravel road located in the Big South Fork National Park in McCreary

County, KY. The objective of this solicitation is to obtain a durable, maintainable, and sustainable end product.

1.3 Contractor workforce performing on the project site during design and construction shall comply with all pertinent provisions of the latest version of US Army Corps of Engineers Safety and Health Requirements Manual, EM 385-1-1.

See MATOC referenced above, FAR Clause 52.236-13 Accident Prevention.

1.4 Federal and State Codes and Regulations. The design and construction of real property improvements shall also comply with all current applicable federal, state and local codes, and with all other applicable laws and regulations governing development, design, and construction at the site. Some state and local codes and regulatory agencies may not have jurisdiction over Federal design and construction on Federal property. The Contractor remains responsible for compliance with the codes and regulations of these agencies, including the reconciliation of conflicting jurisdictional guidance, if any. If certain requirements appear particularly constraining to required constructability or maintainability of the project, the Contractor may recommend the Government (GOV) waive compliance or accept a lesser requirement.

2. PURPOSE AND INTENT

This SOW covers all services required to fully execute a Design-Build project and other supporting activities necessary for design and construction of project features described herein.

Under this Task Order, the Contractor shall provide a complete and turnkey design-build package, including: site investigation and study; pre-final 95% draft plans and specifications, final 100% plans and specifications; and As-

Built/Record Drawings; a construction contractor submittal register; a proposed project schedule (reflecting investigation, design, and construction phases); design narrative and calculations; all personnel, equipment, materials, and services for repair and construction of the roadway, banks, and stormwater system; and any associated or ancillary activities for a complete and usable product.

3. BACKGROUND AND PROJECT DESCRIPTION OVERVIEW

The SOW for this project is to repair portions of Big Creek Boat Dock Road between Big Creek Road and a boat access ramp on the South Fork Cumberland River, approximately six miles north and two miles west of Whitley City, KY. The work will generally include excavating failed gravel road material (subgrade, base, and surface); stabilization of roadway, embankment, and shoulders; and overlay with aggregate to blend in with the existing roadway surface adjacent to the failed area. Investigation of localized stormwater systems, shoulders, and uphill and downhill grade side slopes within the construction limits is a part of the design considerations, as is roadway traffic features and markings, signage, and safety devices (if any are required by law, code, or regulation). Consideration must be given to existing public and private utilities, including a large diameter regional raw water line in the immediate vicinity of the work site, which was partially exposed during the last road failure, and high voltage overhead power lines.

This SOW includes all survey and investigation work within the project area required to produce a complete and usable, turnkey end product. The A-E shall evaluate and determine the necessity of corings and/or geotechnical borings to define conditions in the project area; these services are not required as part of the base SOW, but may be awarded as an Option if determined in the best interest of the GOV. Plans and Specifications will direct the construction contractor to coordinate all work with the NPS and USACE, and with KYTC and McCreary Co. Road Department as may be needed.

Option 1 scope of work includes: All equipment, labor, material, and any other costs associated with obtaining geotechnical boring data from the project site. Additionally, any and all costs associated with boring data analysis and reporting are incidental to the work under Option 0001. If the GOV determines the work covered by Option 0001 to be necessary, then

Option 0001 will be exercised within 90 days of contract award and in coordination with the Contractor’s assumed work sequence and schedule (see Sec 5.3).

4. DESIGN SEQUENCE

4.1 The A-E shall perform the services indicated in this SOW, including exhibits, and pertinent requirements of the

MATOC as guided by this document and its references. These services will be provided in a sequence of deliverable phases that are designed to minimize disruption of Big Creek Boat Ramp Road, the public boat access, and the public utilities within the construction area. These distinct design phases are:

- Project Site Investigation & Kickoff

- Draft 95% Design Package

- Corrected Final (100%) Design Package

- As-Built / Record Drawings (post construction)

Drawings, calculations, specifications, and all other submittal items for this task order will be prepared using English units of measurement.

Project identification shall include the official project title, project number, P2 number (483856), and fiscal year. Project identification shall appear consistently throughout the drawings and specifications.

4.2. Meetings/Conferences. The following is a list of meetings and conferences the A-E shall attend under this Task

Order. The A-E representatives required to attend these conferences are defined below. The exact location, date, and time of each meeting or conference will be established via consultation with the USACE. Participants from the Contractor shall be representatives from the major design disciplines as well as the construction Superintendent, sufficiently experienced and knowledgeable in the project to address GOV questions, comments or concerns at the meeting. Other Contractor team members shall be available via teleconference, if needed. The A-E shall provide a meeting attendees roster, take notes, and prepare minutes for all meetings and conferences attended during design development, including all teleconferences.

Minutes will be prepared in typed form, reviewed by the A-E Project Manager, and furnished to USACE within five days after the meeting/conference for concurrence and distribution to attendees. Copies of all meeting/conference minutes will be included in the Project Narrative.

4.2.1. Initial Technical Coordination Meeting, A-E Investigation, and Project Kickoff. The Contractor shall meet with USACE and the NPS staff to kick off the project, introduce design and construction team members and

GOV POCs, collect any available as-built and record information for the project location, and coordinate work by the field crews doing data collection. The A-E will be required to contact the appropriate local utility authorities to collect any available as-built and record information for the respective impacted utilities. This meeting is anticipated to last 4 hours and will occur at or near the project worksite. The deliverable resulting from this investigation is a site investigation report (with at minimum current site pictures, design assumptions, a project milestone schedule, and a way-forward plan) and review teleconference meeting.

4.2.2. Draft 95% Design Package Review Meeting. A-E shall present Draft 95% Design Package, address review comments to GOV stakeholders. GOV personnel who need to check status and coordinate issues will attend this meeting. The following A-E representatives (or their equivalents for this project) shall participate in this meeting: Project Manager, Civil Engineer and/or Geotechnical Engineer, and other professional design team members as required for a complete review. The A-E will follow-up with comprehensive meeting notes, addressing all comments by GOV stakeholders within 7 days of the Meeting.

4.2.3. Plan-In-Hand Inspection. Not Used.

4.2.4. Corrected Final 100% Design Package Review Teleconference. A-E shall present Corrected Final 100%

Design Package, address review comments to GOV stakeholders to closeout all final GOV review comments.

This meeting will be held via teleconference, and be attended by GOV personnel who need to check status and coordinate issues. The following A-E representatives (or their equivalents for this project) shall participate in this meeting: Project Manager, Civil Engineer and/or Geotechnical Engineer, and other professional design team members as required for a complete review. The A-E will follow-up with comprehensive meeting notes, addressing all comments by GOV stakeholders within 7 days of the Meeting. In the event that the Draft 95%

Design Package and inspection results in no new GOV comments for correction, the Final 100% Draft Design

Package may become the Corrected Final 100% Design Package; a final GOV review teleconference will occur to ensure that all ProjNet/DrChecks (DrChecks) comments are addressed by the A-E and closed by the GOV.

4.2.5. Discussions. The A-E shall provide a written record of all significant discussions and telephone conversations that the firm’s representatives participate in, on matters relative to this project. Copies of these records will be included in the Design Analysis deliverable.

5. SITE VISITS AND INVESTIGATIONS

5.1 Site Visits. The A-E shall visit and inspect the site in sufficient detail to accomplish the development of the design package. The purpose of the visit(s) is to observe and evaluate existing field conditions and to gather supplemental site data necessary for performing the work. Generally, the site visits should be coordinated with the meetings described in Section 4. The Contractor shall notify the NPS POC and the USACE of these visits at least three business days in advance of their occurrence. Reports summarizing the conditions observed, personnel contacted, and data gathered during site visits shall be prepared and included in the Design Analysis deliverable.

5.2. Topographic Surveys. The Contractor and/or DOR shall perform or arrange to have performed topographical surveys as required for this project. Topographic surveys shall be of adequate coverage and accuracy to ensure appropriate design and construction of the roadway and all tie-ins with existing roadway. Survey data shall meet USACE requirements and be provided in NAD-83, NAVD-88 datum; for more particular questions, contact Mr. Alex Fenili, LRN Land Surveyor at Alex.N.Fenili@usace.army.mil or at (615) 736-2046.

5.3. Geotechnical Investigations (OPTION 0001). The A-E shall perform or arrange to have performed adequate geotechnical assessments of the roadway and failure locations within the construction area to determine sufficiently the overall roadway depth and condition for the project area. The exact location, quantity, and type of geotechnical borings shall be determined by the A-E. Payment for Option 0001 covers all equipment, labor, materials, analysis, reporting and all other incidental activities necessary to perform geotechnical investigations. If the work covered by Option 0001 is deemed necessary by the Government, in coordination with recommendations from the Contractor, then the Government will execute Option 0001 within 90 days of contract award. Regardless of whether or not OPTION 0001 is executed, the

A-E is responsible for the adequate and complete design and construction of the roadway repair project, based on the best

A-E engineering judgments and current construction practices regarding existing site conditions.

5.4. Utility Investigations. The A-E shall collect and incorporate utility as-built record documents and utilities investigation information from the utility authorities having jurisdiction (AHJ). The GOV may provide any available record documents and investigations to the A-E to supplement this data; but for the purposes of this solicitation, the A-E should expect to collect all record utility information from the Utility AHJ and perform supplemental surveys as needed.

5.4.1. Field Verification Site Visits: The Contractor will visit and inspect the site as required to verify all conditions affecting design. The A-E will coordinate utility markings and discuss with utility AHJ knowledgeable about the site to identify locations and depths of utilities. The A-E-prepared drawings will show existing utilities to a practical extent, including notating in plans the owners/maintainers of the respective utilities and general notes regarding utility shutoff locations and coordination required by utility AHJ.

5.4.2 Utilities on Site: Utilities impacted by this project may include, but are not limited to, a large diameter raw water pipe within the construction area that runs from the river to a water treatment plant and services the region. Additionally, the project site also has overhead high voltage electric transmission lines in the construction area. The Contractor shall take care to maintain and protect these and any other utilities. As-Built record drawings of the water line can be made available after award. Neither the A-E, nor the construction Contractor, will be allowed to take any utilities out of service during this contract. Further, the A-E and the construction Contractor shall coordinate site operations with the AHJ to prevent interruptions to scheduled or unscheduled maintenance or repairs of the utility, including the water intake, pumping facility, and generator located on Bear Creek Road.

The Contractor is responsible for field verifying all GOV information provided.

5.5 Environmental Investigation. The Contractor shall investigate and incorporate information into the design and specifications with respect to any wetlands, archaeological/historical sites, or habitat of endangered species. The NPS completed an Environmental Screening Form which can be made available after award (see Attachment 9). The GOV does not anticipate or expect any disruptions to the site work because of the presence of wetlands, archeological/historical site, or habitat of endangered species. However, during work, if the Contractor encounters conditions within the work limits which may be considered a wetland, archeological/historical site, or habitat of endangered species, then the Contractor shall immediately contact the COR and halt work on the site until coordination with the GOV is complete. The Contractor shall use applicable permits and associated documentation to assist in the design of the roadway repair. Where and if appropriate, incorporate sustainable design principles into the project.

6. DRAWINGS

6.1. General. The A-E shall prepare drawings in a manner that clearly and adequately delineates the construction work to be accomplished. Design documents will be detailed sufficiently to permit construction contractors to fully construct the road stabilization and repair project described herein. The cover sheet will be signed and stamped by a principal of the firm who is a registered professional engineer in the state where the construction work is to occur. The cover sheet shall contain the project advertisement number.

All design, related documents and document distribution shall meet the requirements defined herein. Any conflicts in design, related documents and document distribution will be clarified upon written request from the A-E. The intent of this agreement is to meet all requirements defined herein and by reference.

6.2. CADD Files. One CADD Sheet File shall be used per drawing (sheet). All design and site condition features will be shown in model files and referenced together to create individual sheet files. CADD designs shall be developed to provide complete project information that will enable the end users to utilize CADD to its fullest. All CADD development shall be based on the understanding that project CADD files will be provided by the GOV to the construction contractor for as-built record drawing purposes, and to the end user for their use. Success in the development of usable as-built record drawings requires a quality product from the A-E designer. To accommodate this, it is required that the A-E will adhere to the following:

6.2.1. Software used (for native files) shall be compatible with the software used by the end user. The design is required be compatible with MicroStation Version 8. Any and all translations are the responsibility of the designers and the designers must have in place a Quality Control procedure to assure the translations are complete and accurate and meet the current technology. Capabilities of translating without loss of quality shall be reported adequately and approved by the Contracting Officer prior to its use. Translations shall not result in the loss of the model/sheet formats of the original drawings, loss of custom characters, loss of distinctive graphics or loss of fonts. If a translation is used, all drawings (hard copy and PDFs) for all submittals shall be plotted from the translated files.

6.2.2. Design file nomenclature and drafting standards shall comply with A/E/C computer-aided design and drafting (CADD) standards. The drawings shall utilize the working units defined in the above noted CADD standards. Drawings shall be on the “ANSI D” size (22” x 34”) sheet. For the final submission, the A-E shall submit the digital drawings in MicroStation file format (.dgn), and Adobe (PDF) format. The A-E shall be able to produce, view, and print MicroStation files, Adobe (PDF) files, and AutoCAD files. Drawing numbers shall be requested by the A-E through Mr. David Kay, LRN Engineering Technician, at David.E.Kay@usace.army.mil or (615) 736-7908. Final drawing package(s) shall be signed and stamped by the appropriate disciplined

Kentucky registered professional engineers, surveyors, geologists, etc. The final drawing package may be digitally signed, and provided in a USACE-approved electronic format.

6.2.3. Unless specifically approved, all projects must provide for all files to be placed in one directory. All unnecessary reference files shall be detached, and all files attached for ‘designer information’ shall be labeled as such in the description field. Where a particularly complex project makes managing all CADD files in a single directory unmanageable, the designer may request permission for use of a more complex directory structure. The designer shall propose the structure, and identify how each individual directory will be used. Where this may result in mapping reference files across directories, the design shall indicate the method for controlling this mapping to prevent loss of files because of remote attachments. It is mandatory that when such a setup is used that mapped directory paths not be used for attachments. Variables shall be used so that project configurations can be created or system variables created for future users to view the files. A description of each variable and mapping shall be provided with electronic file submittals.

6.2.4. The A-E shall have in place a Quality Control procedure that assures all necessary CADD components are provided to USACE and eventually to the end user, including all reference files, resource files, cell libraries, and font files. It is imperative that all files provided include all essential components to replicate the drawings.

6.2.5. In general, the A-E will be required to submit electronic copies as a part of the As-Built/Record drawings in the case of modifications or changes during construction (errors and omissions under this task order, design changes by modification to this task order). All copies should contain identical information.

6.2.6. Electronic files for individual amendments may be required during the project period. It is required that at the end of the construction period that a complete set of revised electronic files be provided that includes updated files for drawings reissued during the PoP. When modifications during construction result in the development of new drawings, the designer shall provide updated electronic files for the new drawings (for errors and omissions under this task order; design changes by modification to this task order).

6.2.7. Contractor shall provide electronic files shall be provided on compact disc at the final deliverable. Each disc shall be clearly labeled with the date of the compact disc (to the day), the level of completion of the files, and project location and name.

6.2.8. At times, native CADD files will be made available to bidders during the bid period. Native files would be provided on an Information Only basis. However, these files shall be complete and match documents produced in the PDF format. Designers must be prepared for this request, and provide a complete set of native files in an organized, easily understood presentation.

6.3. Format. All drawings will be provided in both hard copy and appropriate CADD file format. Full-sized drawings shall be developed as ANSI “D” size sheets and shall utilize the standard US Army Corps of Engineers Nashville District title block. Original drawings and details must be of adequate size, and be clear and sharp to allow the use of half-size reproducible drawings that are legible and easy to read copies.

6.3.1. Drawings shall be clear, ready for reproduction, with line work and lettering clearly legible.

6.3.2. Unless otherwise noted, half-size (11” x17”) drawings are acceptable (see Submittal Matrix).

6.3.3. Provide detailed design drawings such that fabricators have a solid basis of design for shop drawings particularly in the following areas: critical reinforcing details.

6.3.4. Drawing codes and labels: Drawings shall include the 1) Project Number; 2) Fiscal Year; 3) Drawing

Code; 4) P2 Number; and 5) date on the cover sheet and in title blocks. Cover sheet shall include the solicitation number at issue on the “Certified Final”, RTA set and the contract number on the “As-Awarded” set.

6.3.5. All drawings in all submittals shall indicate the status of the design completion at the time of submittal

(i.e., “Concept”, “Final Submittal”, “Certified Final”, etc.; obtain the appropriate terminology to be used from this SOW). All drawings in all submittals shall have the title blocks complete with the first initial and full last name of the Designer, Draftsman, and Checker. All drawings in the Certified Final submittal must be checked, and each page shall be hand initialed by the designer and the checker over the printed name that is displayed in the title block, in addition to “sealing” the drawings by the Designer of Record.

6.4. The following represent Quality Control Measures for Electronic Files that the DOR must implement:

6.4.1. Procedures for assuring translated files are usable and complete representations of the design.

6.4.2. Procedures for assuring all needed files are provided to USACE and the end user for proper and complete use of the CADD files.

6.4.3. Procedure for assuring PDF files provided for advertisement are complete and reflect the design, and that the PDF files provided are complete and correct.

6.4.4. Procedure to assure uniformity between files that includes such items as consistent sheet size (size to be the District standard) and consistent use of a sheet border reference file(s) (as needed) throughout the project.

7. SPECIFICATIONS

7.1. General. The A-E shall provide Specification sections applicable to all necessary disciplines required as part of this SOW for the complete, ready-to-use, turnkey construction package. The specifications shall follow the latest version of the Unified Facilities Guide Specifications (UFGS); Unified Facilities Criteria UFC 1-300-02 “Unified Facilities Guide

Specifications (UFGS) Format Standard;” and USACE Engineering Regulation ER 1110-1-8155 “Engineering and Design

– Specifications” to the maximum extent possible. The Specifications shall be edited and maintained in the SpecsIntact software. The specifications provided as part of this SOW shall be prepared following the latest edition of the CSI Master

Format. USACE and LRN-specific Specifications and SpecsIntact access, format, questions, etc. shall be coordinated with

Mr. Larbi Kandil, P.E. (615) 736-7907, Larbi.Kandil@usace.army.mil of USACE LRN.

The Contractor shall include all required construction submittals in properly formatted paragraphs in the body of all specification sections. The SpecsIntact software will automatically generate the submittal schedule (ENG Form 4288) outlining shop drawings, product or miscellaneous information, assembly instructions, warranties, certificates, or submittals required in the body of the specifications. The A-E shall furnish this submittal schedule as part of the specifications. Vendor quotes shall also be provided to the GOV.

The Contractor is responsible for ALL technical specifications. Any required pertinent specifications from

KYTC, state environmental, etc. specifications shall be converted into UFGS guide specification format. The A-E shall use the latest version of all specifications. Examples of specifications and their web links are listed below for information purposes; these may not constitute all other third-party Specifications to be used.

7.1.1. Unified Facilities Guide Specifications (UFGS): http://www.wbdg.org/ccb/browse_org.php?o=70.

7.1.2. Kentucky Transportation Cabinet (KYTC): https://transportation.ky.gov/Pages/Home.aspx.

7.1.3. Some Specifications, such as environmental related specifications, may be provided separately or by the

NPS or from state or local AHJ and shall be incorporated as appropriate within the defined text and format.

7.2. At the 95% Pre-Final Design stage, the A-E shall provide draft specifications used for the project. Sections shall be arranged within their respective divisions, in numerical order. New specification sections, developed by the A-E, will be numbered to fall in their respective division at a logical location.

7.2.1. Division 00 – Not Used

7.2.1.1. The GOV retains responsibility for preparation of Division 00 contract clauses.

7.2.1.2. Section 00 80 00 SPECIAL CLAUSES. Not Used.

7.2.2. Division 01. Not Used.

7.2.3. Divisions 2 through 48. The A-E shall edit and adapt USACE guide specs as appropriate to satisfy the project requirements and provide a complete set of construction specifications. Where there are no appropriate guide specifications available for use, the required specifications will be prepared by the A-E using common and typical construction industry format, language, and directives. These specifications shall be developed in the same format as UFGS, numbered appropriately to fit logically within the appropriate specification division and shall list the essential features, functions, and other factors to clearly indicate the type and quantity of items/work required including any required submittals. All specifications will be prepared by listing parameters and requirements that can be met by several manufacturers. The A-E should avoid the use of trade names and proprietary items in the design and specifications.

7.3. Project codes and labels: Specifications and report cover sheets shall include the 1) Project Number; 2) Fiscal

Year; 3) P2 Number; and 4) date in addition to the development phase of the project design. The Specifications cover shall include the solicitation number and the contract number on all sets.

7.4. Page numbering will restart at the beginning of each section.

7.5. Construction Contractor Submittal Register.

7.5.1. The specifications require the construction contractor to submit shop drawings, samples, manufacturer’s data, certificates, test reports, and other items to the GOV. The A-E shall prepare a complete listing of construction contractor submittal requirements on Eng Form DD 4288 using SPECSINTACT. These submittals will be classified as either “Government Approval” or “For Information Only.” All non-critical submittals should be classified as “For Information Only,” or as directed by USACE CD personnel. Those submittals that are critical to safety, construction execution, and system or facility operation should be classified as “Government

Approval.” The type of submittals requiring GOV approval are extensions of design, critical materials, deviations, O&M manuals, or those involving equipment that must be checked for compatibility with the entire system. The only review code classifications that shall be used are “G”, or “G AE”. A-E effort for submittals labeled “G AE” is covered in paragraph 13. Any additional A-E effort identified during the design process shall be address through contract modification.

7.5.2. The A-E shall edit the submittal portion of each specification section in accordance with SECTION 01

33 00 – SUBMITTAL PROCEDURES. The A-E shall coordinate submittal requirements for each specification section with USACE Area Construction Office and with Nashville District Construction Division Office before submittal of the final design. The Submittal Register Form (DD 4288) created from SPECSINTACT shall be provided for final design review and must be approved by USACE CD personnel for inclusion in the final specification package.

7.5.3. The Submittal Register .TXT data file (DD 4288.txt) created from SpecsIntact, which is used to transfer submittal requirements to RMS, the COE construction management system shall be provided with the RTA and

As-Awarded submittals.

7.5.4. The following submittals will require GOV approval at least 30 days prior to procurement or performance of the work.

Preconstruction Submittals (Construction Quality Control Plan in accordance with technical specification 01 45 00; Accident Prevention Plan in accordance with technical specifications

01 35 26; Site Specific Spill Prevention Plan; Stormwater Pollution Prevention Plan; and

Activity Work Plan)

All submittals pertaining to excavated material and waste disposal plans

Material storage and parking area plans (reviewed and approved by GOV prior to storage)

Riprap and Stone gradations

Geotextile plan (if used), to include woven, non-woven, mesh sizes, etc.

Pre-construction and Final surveys

Design Data (calculations, descriptions, or documentation regarding the work)

Quality Control Daily work reports

All submittals pertaining to Test Reports (inspections or tests, including analysis and interpretation of test results)

Manufacturer’s Instructions (printed materials describing installation of a product, system, or material; including special notices and safety data sheets, if any, concerning impedances, hazards, and safety precautions)

Closeout submittals (all data, documentation, information, and drawings to achieve Task Order contract closeout)

Schedules

Records

7.6. The Final Design Submittal native files version of specifications shall be submitted with “revisions” toggle on so that revisions made to the original, native specifications can be easily recognized during review. PDF version shall have

Revisions toggle off so that the final version is seen “as edited”. For paragraphs that are deleted entirely, the titles remain followed by “NOT USED”.

8. PREPARATION OF ELECTRONIC FILES

8.1. The Contractor is responsible for providing the electronic files. The standard consists of plans (drawings) to be in electronic format (PDF) and specifications to be in PDF format, and any PDF files shall be scalable. The A-E is responsible for obtaining all software required to create these files. Drawings shall be created which allow for printing the electronic files legible at both full size and half size. Electronic submittal of these documents shall be complete and identical to the signed drawings.

8.1.1. In addition to the plans and specification files, the Contractor shall provide a listing of all PDF drawings that contain the electronic filename, the sheet reference number, and the sheet description. They shall also provide the PDF filename and the section number and section title for specification files. The preferred software format for this information is Microsoft Excel.

8.1.2. Files to be used for As-Built Record Drawings shall be provided by the Contractor to USCE and NPS as a complete set of documents. Replacement of individual files will not be acceptable. For amendments, electronic files can be provided either by compact disc or by posting to a GOV maintained FTP site. Instructions for the

FTP site shall be provided by the COR as required.

8.2. Scanning of Files. The DOR shall be responsible for providing all information in electronic format. This may require the scanning of paper records or documents. For documents to be included in the specification package of PDF files, all files shall be provided in standard letter size printing. The files shall be imported into appropriate word processing software and printed into PDF format as with the other specification items. The files shall be scanned at 300 dpi to assure adequate resolution.

8.3. The Contractor is required to submit files on CD in final form. USACE uses Adobe Acrobat for viewing the specifications and drawings.

8.3.1. As-Built Record Drawings and Documents

8.3.2.1. At the end of the construction phase, the Contractor shall provide project as-built record drawings to GOV. Electronic format should be sent via CD, labeled with project name, number, date, Contractor information, and other pertinent project information.

8.3.2.2. The DOR shall also provide native files to the Contractor in preparation of as-built record drawings. These electronic files shall be submitted via DVD (or other media as approved by USACE) and shall be organized and presented in a way in which the Contractor can easily identify proper files for updating. Native specification files shall also be provided.

8.3.2.3. In compliance with the standard to provide CADD files in the format used by the end user, the designer shall not translate any files to other formats for use by the Contractor during the construction/as-built preparation process.

9. CONSTRUCTION COST ESTIMATING

9.1. As this is a lump sum, turnkey Design-Build project, no cost estimating is required as a formal deliverable of this

SOW. However, the Contractor is solely responsible for assuring that the design methodology and construction processes are managed within budget of the awarded project. Differing site conditions, if any, are not automatically sufficient reasons to modify the cost or schedule of this project and USACE will review these on a case-by-case basis.

10. QUALITY CONTROL

10.1. Quality Control (QC) Plan (QCP). The Contractor shall submit a draft QCP with the bid package. Within 14 days after Task Order award, the A-E shall provide a completed QCP that contains at minimum:

10.1.1. Identification and discussion of all organizational and technical interfaces.

10.1.2. Design/Study team members to include their assignment and areas of responsibility.

10.1.3. Team members responsible for checking the design, i.e., not the same person as the designer. Each critical project discipline shall have a designer and checker.

10.1.4. Team members responsible for checking the electronic files.

10.1.5. Project schedule showing key milestones and review periods for GOV review.

10.1.6. Identification of the methods to be used for management of review comments.

10.1.7. QC procedures for assuring end product native CADD files are acceptable for use by the user and can be transformed into formats required for electronic advertising.

10.1.8. QC procedure to assure that PDF files produced for advertising are identical to the documents submitted for review.

10.1.9. Brief narrative describing the processes necessary to design sustainability into this project.

The A-E is responsible for product development, internal QC, and technical review for all products provided under this contract. The QCP must be approved by the USACE COR before proceeding with any work.

10.2. Independent Technical Reviews (ITR). Not Used.

10.3. Quality Assurance. USACE will perform a quality assurance (QA) review of all work to assure compliance with the A-E contract. USACE will review the work of the A-E during each phase of design and return comments using the

DrChecks web-based automated management system. Submittals should require only policy and scoping assurance with minimal technical review by the GOV. The GOV will not review quality into the design. GOV review DOES NOT relieve the A-E of responsibility for the design. The GOV may return to the A-E for correction, completion and resubmission any submitted work that shows technical or coordination deficiencies. Contractor rework does not automatically guarantee an extension of the PoP. Costs associated with A-E rework and resubmission shall be borne by the A-E, and no schedule time extension should be expected for rework and resubmittal.

11. MISCELLANEOUS REQUIREMENTS

11.1. Proposed Construction Schedule. The A-E shall prepare a baseline schedule using software capable of producing a Gantt chart. During development of this schedule, due consideration will be given to standard construction practices, durations of tasks, the sequence of construction, procurement of materials, climatic conditions, etc. The Proposed

Construction Schedule should be in the form of a Gantt chart. The construction schedule shall include start and finish dates for each activity and the total duration for the activity. It shall also include cost loading showing the cost for each activity. The costs shall correctly reflect those associated with their specific activity, and unbalanced cost loading will not be accepted. The costs for each individual activity shall sum to the total construction cost in accordance with the construction bid items in the contract. The following is a minimally acceptable list of construction activities that shall be included in the baseline schedule: contractor mobilization, site preparation, erosion protection and sediment control installation and maintenance activities, clearing and grubbing, excavation and demolition, backfill, road gravel placement, tree removal (if any), rock or boulder removal, riprap placement, final site stabilization, cleanup, contractor demobilization.

11.2. Project Narrative (PN). – Not Used.

11.3. Engineering Considerations and Instructions to Field Personnel (ECIFP) Report. Not Used.

11.4. Operations and Maintenance Manual. Not Used.

11.5. Correspondence and Permits

11.5.1. Discussions. Correspondence with all agencies and individuals shall be included in minutes identifying person(s), titles, agencies, time, and date. Brief synopsis of discussion identifying key points and the “take away.”

The Contractor shall provide a written record of all significant discussions and telephone conversations that the firm’s representatives participate in, on matters relative to this project. Copies of these records will be included in the Final Deliverable package for USACE record, but may be requested at any time during the PoP in the case of USACE questions regarding the design package or construction efforts.

11.5.2. Permits. Determine and report on any permits required for the project. Ensure that designs comply with regulations. Determine and fill out Permits Matrix. Identify all permit requirements, and obtain permit application forms.

12. RESPONSIBILITY AFTER DESIGN COMPLETION

12.1 Design Document Corrections/Clarifications. The DOR is responsible should any errors or omissions in the documents create problems during construction. As needed, the DOR shall clarify the design and correct any errors and omissions in the original documents (plans, specifications, calculations, design narrative, etc.). The corrections shall be performed and resubmitted in a timely manner as to avoid construction delays and at no additional cost to the GOV. The

A-E shall incorporate changes on the original drawings and/or CADD drawings when requested at no extra cost to the

GOV. In addition, the A-E shall incorporate changes on the specifications and submittal registers and submit one copy in the SPECSINTACT format. All drawings and specs shall be on a DVD or CD labeled with the project title, location, and construction contract number at final completion.

13. SUBMITTALS REVIEW PROCESS AND PERFORMANCE SCHEDULE

13.1. Distribution of Submittals. Submittals shall be processed in accordance with technical specification 01 33 00 and

01 45.00 15 utilizing the GOV’s Resident Management System. Deliverables for each phase of design development shall include softcopy native files and hard copies of all drawings as indicated in Attachment 2. Narrative and text documents, specifications, project narrative and cost estimates will be provided in GOV approved electronic formats and hard copies.

All electronic files shall be furnished on recordable CDs. The distribution list and number of copies of each document are shown in Attachment 2 Submittal Matrix. Distribution list addresses are provided in Attachment 3.

13.2. GOV Review and Comment Resolution. The GOV will review all submittals identified under this task order.

Formal comments generated during the review will be provided to the A-E through the DrChecks automated review management system, and the A-E will respond to all comments via DrChecks. Both parties will discuss these comments, if necessary, and attempt to resolve any unsettled issues that may arise from the review. The period for GOV review and comment resolution generally will be 14 calendar days. Respond to all comments verbally at review meetings, and in writing through DrChecks within 7 calendar days of the actual review meeting. The written responses will be included in design analysis at each submittal phase.

13.2.1. Review Process. Specific description of the review process follows:

13.2.1.1. DrChecks: In accordance with ER 1110-1-8159, DrChecks (Design Review and Checking

System) a web-based design review management system that facilitates, documents, and tracks the review process will be used for all formal reviews conducted by the A-E or the GOV for this project.

The DrChecks system has six categories of users – “Comment Submitters”, “Comment Evaluators”, “Comment Back Checkers”, “Review Managers”, “Design Managers”, and “View Only Access”. In most cases, the A-E will serve in one or more of the first three categories.

13.2.1.2. When the A-E is ready to conduct a review, the A-E Project Manager shall contact USACE to request a review be added to DrChecks. At this time, the A-E Project Manager will identify persons to review as “Comment Submitters”, “Comment Evaluators”, “Comment Back Checkers”, “Review

Managers”, “Design Managers”, and “View Only Access” the name of the review, and the start and stop dates of the review. The USACE will then add the review setup information into DrChecks and give access to the appropriate personnel. Those who have not previously registered in the DrChecks system will need to do so before they can carry out their comment evaluation obligations. Registration is simple and takes less than five minutes. DrChecks can be accessed via the internet at https://www.projnet.org/projnet/binKornHome/index.cfm. A DrChecks resource webpage has been created to provide background information as well as links to training modules. The PowerPoint presentations provide detailed instructions on how to register and use the system as well as detailed instructions for the A-E.

13.2.1.3. USACE project partners are encouraged to enter all comments via DrChecks. However, some review comments may be provided to the A-E by email, fax, paper copy, or verbally at meetings.

The A-E shall enter these comments in the DrChecks project database and shall respond to all comments through the DrChecks system. The Lessons Learned feature shall be utilized at the Final Design

Submittal review for recording Lessons Learned during project development.

13.2.1.4. In the Corrected Final submittal, submit a separate set of plans and specifications marked in red with the name of the commenter and comment number where each comment was incorporated and addressed.

13.2.1.5. Provide a certification signed by the project principal, with each submittal, certifying that all pertinent review comments have been incorporated into the submittal.

13.3. Performance Periods and Submission Schedules. The performance periods and submission schedules for each milestone phase is provided (see Attachment 4). All days listed are calendar days. Time for internal reviews, reproduction, distribution, and mailing is inclusive to the stated durations. The A-E may choose to perform work at its own risk during the GOV review and comment period; however, comments resulting from reviews must be incorporated into the design prior to the next submittal regardless of rework.

If at any time during PoP circumstances present themselves which will not allow the requirements stated herein to be met, the contractor shall notify the COR immediately in writing explaining the circumstances. Completing projects timely and in accordance with this SOW is critical to meeting client expectations; failure to meet schedule requirements may adversely affect Contractor performance evaluations.

14. CONTRACT AUTHORITY

The A-E shall only accept instruction from the Contracting Officer or the duly appointed representative, and only do work that is covered by SOW of the Base Contract and any executed option. Only the USACE Contracting officer can modify this Task Order. Direct requests from other agencies should be forwarded to the COR. Coordination of routine technical matters with USACE personnel shall be through the COR.

15. REQUESTS FOR PAYMENT

15.1. Pay Estimates: The A-E Contractor shall submit Pay Estimates using ENG Form 93, Payment Estimate - Contract

Performance. ENG Form 93 may be found on the Internet at:

https://www.publications.usace.army.mil/USACE-Publications/Engineer-Forms/

Requests for payments and requests for retainage refunds shall be submitted on the same ENG Form 93. All ENG Form 93 shall be submitted to the COR in electronic (pdf) format. Pay estimate shall be submitted to the COR for review and processing with USACE Millington, TN finance center.

15.2. Progress Reports: The A-E shall include a progress report with the ENG Form 93, Payment Estimate as justification for the amount of payment requested and address the period of work covered by the ENG 93. The progress report shall include in narrative form a summary of activities, estimated percentages completed, project schedule evaluation, a 10-day and 30-day look ahead, and shall note any problems encountered by the Contractor and recommended solutions. Pay Estimates should be submitted directly to the COR.

15.3. Release of Claims: A Release of Claims shall accompany the final ENG Form 93. COR will provide LRN Form

96 Release of Claims to the Contractor. The Release of Claims shall be signed by a contractor company employee with signatory and contract-binding authority, and include the final Task Order amount.

15.4. Contractor Manpower Reporting

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection website where the Contractor shall report all Contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor is required to fill in all the information in the format provided at: https://www.ecmra.mil and all reporting is annual. Data for each separate contract is entered at the completion of the contract or the end of each Fiscal Year, whichever comes first. Deadline to enter data is 31 October of the reporting year.

16. SPECIAL TASK ORDER ADMINISTRATION REQUIREMENTS

16.1. It is mutually agreed by the Contractor and the GOV that the MATOC Contract will remain open through the construction period of the project for which this Task Order relates, or until release of claims…