Appendix_A_-_Technical_Specifications.pdf

Solicitation No. W5J9JE-16-R-0005

US Army Corps of Engineers Transatlantic Afghanistan District

AFGHANISTAN NATIONAL ARMY (ANA)

Force Protection Upgrade at Hamid Karzai International Airport (HKIA)

Kabul Province, Afghanistan

Site-Adapt Project Specifications And Drawings

Proposal Requirements, Contract Forms, Conditions of the Contract

November 2015

This page was intentionally left blank for duplex printing.

TABLE OF CONTENTS

SOLICITATION PROVISIONS, CONTRACT CLAUSES AND SPECIFICATIONS FOR:

Force Protection Upgrade at Hamid Karzai International Airport (HKIA)

Kabul, Afghanistan

DIVISION 00 – PROCUREMENT AND CONTRACTING REQUIREMENTS

Section Title

00010 Bidding Schedule

APPENDIX A TECHNICAL SPECIFICATIONS

DIVISION 01 - GENERAL REQUIREMENTS

Section Title

01 10 10 Scope of Work 01 10 15 Technical Requirements 01 32 17 Network Analysis Schedule 01 33 00 Submittal Procedures 01 35 13 Special Project Requirements 01 35 26 Government Safety Requirements 01 35 53 Site Security 01 42 15 Metric Measurement 01 45 00 Contractor Quality Control 01 45 05 Quality Control System (QCS) 01 57 20 Environmental Protection 01 78 00 Closeout Submittals

DIVISION 02 - EXISTING CONDITIONS

02 41 00 Demolition

DIVISION 31 - EARTHWORK

31 00 00 Earthwork 31 11 00 Clearing and Grubbing 31 32 11 Soil Surface Erosion Control

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 11 16 Aggregate Base Course 32 31 13.00 10 Chain Link Fences and Gates

TABLE OF CONTENTS

Table of Contents - Page 2

APPENDIX B OVERALL SITE PLAN

APPENDIX C LICENSED FOR CONSTRUCTION LETTER

APPENDIX D PRIORITY 1 – WEST & NORTH PERIMETER FP

APPENDIX E PRIORITY 2 – PEH COMPOUND FP

APPENDIX F T-WALL GRAVEL BASE

APPENDIX G GUARD TOWER T-WALL PLACEMENT

APPENDIX H CONCERTINA WIRE BRACKETS

APPENDIX I NOT USED

APPENDIX J T-WALL BARRIER STANDARD DRAWINGS

(REFERENCE)

APPENDIX K SNIPER SCREEN

APPENDIX L T-WALL OFFSETS

– END OF TABLE OF CONTENTS –

SECTION 00010

BIDDING SCHEDULE

Provide a price for all items. The Government will evaluate the Contractor’s entire proposal to determine which CLINs represent the best value to the Government.

CLIN Description Qty Unit Unit Price Total Amount

Base Bid Items Proposal:

0001 Mobilization / Demobilization 1 Job xxx $

0002 Priority 1: West & North HKIA Perimeter 1 Job xxx $ Security improvements

0003 Priority 2: Improve Perimeter Security, PEH 1 Job xxx $ Compound, South HKIA

Total Estimated Base Bid Amount $

TOTAL PROPOSAL FOR ALL ITEMS: $

Abbreviation:

Qty = Quantity

-END OF SECTION-

This page was intentionally left blank for duplex printing.

Section 01 10 10 - Page 1

SECTION 01 10 10

SCOPE OF WORK

1. GENERAL

The project consists of the procurement, execution, and management of a Force Protection Upgrade project at Hamid Karzai International Airport (HKIA), Kabul, Afghanistan, in support of the Afghan Air Force and Afghan Special Mission Wing (SMW) missions. Refer to paragraph 1.6.1 SITE BOUNDARIES contained herein and the overall Site Plan in Appendix “B” for approximate site location.

1.1 DEFINITIONS

For this Contract, the term “Government” is defined as the Contracting Officer for the U.S. Army Corps of Engineers, Transatlantic Afghanistan District.

1.2 REFERENCES

The work of this Contract shall meet and be constructed in accordance with the U.S. design standards and technical references as indicated in Section 01 10 15 TECHNICAL REQUIREMENTS.

1.3 SUBMITTALS

Submittals and a Submittal Register are required as specified in Section 01 33 00 SUBMITTAL PROCEDURES of the Contract.

SD-01 Preconstruction Submittals

Contractor Quality Control Plan; G, RO Security Plan; G, Safety Office Accident Prevention Plan: G, RO Network Analysis Schedule: G, RO

SD-02 Shop Drawings

T-Wall Product Data; G, RO Sniper screen wall attachment plan: G, RO

1.4 QUALITY ASSURANCE

1.4.1 LINGUIST REQUIREMENT

a. All official communication between the Contractor and the Government shall be presented in English.

b. At all times during the performance of this Contract, and until all work is complete and accepted, the Contractor shall have a minimum of one representative (Linguist) on site that is fluent in both English and the local language.

c. The Linguist shall attend all meetings with the Government.

d. The Contracting Officer's Representative (COR) will approve of whom the Contractor provides as its Linguist. At any time, upon the request of the COR, the Contractor shall remove the Linguist from its staff and replace with another until found to be satisfactory for contractual communication as determined by the COR.

e. A satisfactory Linguist shall be defined as a person with the ability to:

1. Convey verbal information in English to the Government in a clear and concise manner;

Section 01 10 10 - Page 2

2. Receive and understand verbal information in English from the Government in a clear and concise manner;

3. Read and write the English language in a clear and concise manner; and

4. Convey, communicate, and interpret information in both English and the local language between all multiple language parties at meetings, site visits, in official letters and e-mails, and all other contractual communications as required.

1.4.2 CONTRACTOR QUALITY CONTROL

1.4.2.1 QC MANAGER TRAINING REQUIREMENT

See Section 01 45 00 CONTRACTOR QUALITY CONTROL for Contractor’s QC Manager training requirements.

1.4.2.2 QUALITY CONTROL SYSTEM (QCS)

The Contractor’s quality control plan, as defined in Section 01 45 05 QUALITY CONTROL SYSTEM (QCS), must include the name qualifications (in resume format), duties, responsibilities, and authorities of each person assigned a Contractor Quality Control function. For the QC Manager, qualifications must include a certificate demonstrating completion of an approved CQM course.

1.5 SCHEDULE

The following is an internal schedule outlining the milestones for Completion of Work and is subject to modification by the Offeror to suit their particular method of operation. The submittal milestones are described in Section 01 33 00 SUBMITTAL PROCEDURES. Overall time constraints are required and cannot be changed except by contract modification. The successful Contractor shall be required to submit a complete schedule for this construction that meets or exceeds the overall time goals of the Government for this project.

ACTION / SUBMITTAL ITEM

TIME FROM LAST ACTION

(IN CALENDAR DAYS)

Notice to Proceed (NTP) Following Written Notification of Contract Award

Pre-construction Conference Within 7 days following NTP

Project Schedule & submittals Within 14 days following NTP

Construction Period (Priority 1) Completed within 210 days of NTP

Total Project Construction Period Completed within 295 days of NTP

1.6 PROJECT AND SITE CONDITIONS

1.6.1 SITE BOUNDARIES

a. The Licensed for Construction (LFC) site boundaries are defined by the coordinate points as shown in Appendix “C”.

b. The Contractor shall verify the accuracy of the coordinates provided herein, and submit to the COR for approval. The development of the site and construction of all permanent structures is required to be fully within this defined LFC area. The Contractor shall notify the COR immediately should the development of the proposed site require an encroachment beyond the LFC boundary. The Contractor shall obtain the necessary approval for the access road connecting the proposed site to an existing road. Submittals shall include a site plan illustrating the limits, boundaries, access roads, and coordinates representing the LFC area.

Section 01 10 10 - Page 3

1.6.2 SITE VISIT

It is the responsibility of the Contractor to have visited the site prior to submitting its proposal for the project and to have gained a good understanding of the project and its requirements, including grading and drainage details necessary to appropriately submit its proposal and construct the project.

1.7 SECURITY

a. Security is critical to construction in Afghanistan, especially on roads and remote areas away from Coalition Force bases.

b. The Contractor shall provide an appropriate level of security and protection to match the threat that exists in the project area and along the supply routes. A detailed security plan in accordance with Section 01 35 53 SITE SECURITY shall be provided by the Contractor, and must be approved by the Government, prior to issuing a construction Notice to Proceed.

1.8 UNEXPLODED ORDNANCE (UXO)

1.8.1 PREVIOUS SITE CLEARING

The Contractor shall assume no mines or unexploded ordnances (UXO) exist on the site. If, during construction, the Contractor becomes aware of or encounters UXO/Mine or potential UXO/Mine, the Contractor shall immediately stop work at the site of encounter, clearly mark the area of UXO/Mine, move to a safe location, notify the COR, and mitigate any delays to scheduled or unscheduled Contract work.

Once the Contractor has informed the COR, the Contractor will await further direction.

1.9 CONSTRUCTION PROJECT SIGN

The contactor shall fabricate and display at least one sign to identify the project site as an Islamic Republic of Afghanistan sponsored project. The sign shall meet or exceed the requirements provided in Section 01 35 13 SPECIAL PROJECT REQUIREMENTS. Exact placement of the sign at the project site shall be coordinated with the COR.

2. SUMMARY OF WORK

2.1 PRIORITY 1: WEST & NORTH HKIA PERIMETER SECURITY IMPROVEMENTS

Locations for this work are shown on Appendix “D”.

a. Prepare ground surface for T-wall placement (approximately 3,025 meters) o Grade and level site, place and compact gravel base

• Compacted gravel base shall be 300mm (H) x 1.8m (W) x 3,025 meters (L)

• The compacted base shall be of 40-50mm crushed angular stone installed in two compacted lifts of 150mm each

• Final Compaction shall be 98% and able to support concrete T-Walls. Minimum soil compaction shall be 98 percent of maximum density as defined in ASTM D 1557. See Appendix “F”.

b. Install approximately 3,025 meters of “interlocking Alaska-type barriers” (or equal), 3.7 meters tall, at location shown in Appendix “D”. See Appendix “J” for sample T-wall descriptions.

c. At location for guard towers shown in Appendix “D”, line of the wall will go to the outside of the guard towers. At this location, provide three (3) interlocking T-walls, 3 meters tall, in front of (outer side of base) each guard tower, with suitable gravel base as described above. See Appendix “G”.

d. Remove and Relocate 395m of existing T-walls that are 3.35m tall or shorter to TAAC-Air Laydown Yard. See location on Appendix “D”.

Section 01 10 10 - Page 4

e. Remove and dispose of existing “Hesco-type” earthen barriers (approximately 170m) at location shown on Appendix “D”. Debris and barriers shall be taken to debris disposal site shown in Appendix “B”.

f. Fabricate and install “U” brackets for triple stranded concertina wire (Concertina-Wire), 3 meters on center, along top of T-Walls (3,025m) for installation of triple-stranded Concertina-Wire. See Appendix “H”.

g. Provide and install filled sandbags to fill in gaps between T-walls wherever there is a turn/angle in wall sections or as required (approximately 500 sandbags).

h. Along most westerly location of new T-walls: place adjacent to existing rock wall and chain link fence as shown in Appendix “D”. T-walls shall be placed as close to the chain link fence as possible), on the inside of the compound

i. Contractor to provide fabrication plans, for approval by the Contracting Officer or his/her representatives, for the construction of the T-walls. At a minimum, the following shall be observed:

o T-wall concrete shall be a minimum of 4,500 psi at 28 days o Rebar:

• Handle Rebar Steel Dia 20

• Vertical Rebar Reinforcement Steel gauge dia 18

• Horizontal rebar Reinforcement Steel gauge dia 10

• Rebar Spacing (maximum spacing between joints) 20cm

j. No structures that have been damaged in shipment and installation will be accepted. All structures are to be new and not damaged. No chips, cracks, voids, etc will be accepted.

2.2 PRIORITY 2: IMPROVE PERIMETER SECURITY, PEH COMPOUND, SHKIA

Locations for this work are shown on Appendix “E”.

a. Prepare ground surface for T-wall placement (approximately 670 meters) o Grade and level site, place and compact gravel base.

• Compacted gravel base shall be 300mm (H) x 1.8m (W) x 670 m (L).

• The compacted base shall be of 40-50mm crushed angular stone installed in two compacted lifts of 150mm (H) each.

• Final Compaction shall be 98% and able to support concrete T-Walls. Minimum soil compaction shall be 98 percent of maximum density as defined in ASTM D 1557. See Appendix “F”.

b. Place approximately 670m of 6m-high T-walls (Interlocking Alaska barriers, extra-large, or equal).

See Appendix “J”. Attach chain link sniper screen fence to top. Contractor to provide plan for attaching sniper screen fence securely to T-wall. Attachment work will not begin until approval of plan by Contracting Officer or his/her representative. See Appendix “K”.

o Fabricate and install chain link fence poles 65mm (dia). Chain link fence line posts shall be inset into the T-wall no less than 600mm deep and extend 2m above T-wall.

o Chain link Fence shall be installed the length of the T-wall (approx. 670m) o Constructed T-wall and chain link fence shall be no less than 8m in height.

c. Provide and install filled sandbags to fill in gaps between T-walls wherever there is a turn/angle in wall sections or as required (approximately 250 sandbags).

d. Where installation of T-walls will cover existing sanitary or storm drain manholes, the line of T-walls will be staggered, as shown in Appendix “L”.

Section 01 10 10 - Page 5

e. An existing rock perimeter wall is located along the intended placement of the T-walls. T-walls shall be placed adjacent to existing rock perimeter wall (as close to the wall as possible), on the inside of the compound, as shown in Appendix “E”.

f. No structures that have been damaged in shipment and installation will be accepted. All structures are to be new and not damaged. No chips, cracks, voids, etc will be accepted.

2.3 CIVIL

2.3.1 DEMOLITION

a. Demolition shall include clearing and grubbing of the site, and the removal of all existing structures, foundations, pavements, and utilities. All refuse and debris shall be promptly and properly disposed of off-site.

b. Holes and depressions shall be backfilled and compacted in lifts not to exceed 150 mm in height unless specified otherwise. Fill materials shall be composed of satisfactory soils or aggregates defined in ASTM D 2487 as GW, GP, GM, SP, SM, and SW. Minimum soil compaction shall be 95 percent of maximum density as defined in ASTM D 1557.

c. Scrap metal shall become the property of the Host Government. The scrap metal shall be moved to an area away from the site perimeter, or areas of ongoing site work, as directed by the Contracting Officer’s Representative, and left for the Host Government to remove and/or salvage. Demolished fencing and concertina wire shall be neatly rolled up for reuse by the Host Government.

Demolished fence posts and outriggers shall be neatly stockpiled for reuse by the Host Government.

d. T-walls removed as part of this project shall be relocated to the TAAC-Air Laydown Yard site shown on Appendix “D” and turned over to the COR or his/her representative.

2.3.2 GRADING

Grading will be required to provide a flat surface for the placement of the T-walls. Preparation of the base for the placement of the T-walls shall be in accordance with paragraphs 2.1.a and 2.2.a above.

3. EXECUTION

3.1 CONTRACT PLANS AND SPECIFICATIONS

Contractor shall construct all features of Contract work in complete accordance with contract plans and specifications furnished by the Government unless noted otherwise and stated herein. Refer to the appendices for provided plans and layouts.

3.1.1 ORDER OF PRECEDENCE

In case of conflict, duplication, or overlap of criteria specified in the documents referenced in this Contract, the following order of precedence shall be followed:

1. Contract Award Document and referenced publications therein;

2. Written requirements and specifications;

3. Drawings.

3.2 CONTRACT DOCUMENTS

3.2.1 TECHNICAL SPECIFICATIONS

a. The Technical Specifications, included in Appendix A, are provided for work to be performed and materials to be installed by the Contractor as directed by the plans provided by the Government. All

Section 01 10 10 - Page 6 technical, testing and submittal requirements shall be adhered to as described in each respective specification.

b. The Contractor shall prepare and submit for approval in accordance with Section 01 33 00 SUBMITTAL PROCEDURES any technical specification required for construction of the plans provided by the Government.

3.2.2 ORDER OF PRECEDENCE

In case of conflict, duplication, or overlap of criteria specified in the documents referenced in this Contract, the following order of precedence shall be followed:

4. Contract Award Document and referenced publications therein;

5. Written requirements and specifications;

6. Drawings.

-- END OF SECTION --

Section 01 10 15 - Page 1

SECTION 01 10 15

TECHNICAL REQUIREMENTS

1.0 GENERAL

1.1 COMPLIANCE

The Contractor's design and construction must comply with technical requirements contained herein. The designer shall have a minimum of 5 years experience with the design and construction of projects of the same magnitude and complexity as required in this project. The Contractor shall provide design and construction using the best blend of cost, construction efficiency, system durability, ease of maintenance and environmental compatibility.

1.2 ASBESTOS CONTAINING MATERIALS

Asbestos containing material (ACM) shall not be used in the design and construction of this project. If no other material is available which will perform the required function, or where the use of other material would be cost prohibitive, a waiver for the use of asbestos containing materials must be obtained from the Contracting Officer.

1.3 LIMITATION OF WORKING SPACE

Except where required for service connections or other special reason(s), the Contractor shall confine his operations strictly within the boundaries of the site. Workmen will not be permitted to trespass on adjoining property. Any operations or use of space outside the boundaries of the site shall be by arrangement with all interested parties. The Contractor shall take all practical steps to prevent his workmen from entering adjoining property, and in the event of trespass occurring the Contractor will be held entirely responsible.

Areas located immediately outside the site boundaries and construction area may contain mines and unexploded ordnance (UXO). Contractors assume all risks when venturing in or out of the designated work area.

1.4 TEMPORARY STRUCTURES

The Contractor shall erect suitable temporary fences, lighting, and necessary structures to safeguard the site, materials and plant against damage, theft, and protection of the general public; and shall adequately maintain the same throughout the course of the Contract.

1.5 SUBCONTRACTORS

Compliance by all subcontractors with the provisions of this section shall be the full responsibility of the Contractor.

1.6 TECHNICAL REFERENCES

1.6.1 LIST OF CODES AND TECHNICAL CRITERIA

ACI 301M Specifications for Structural Concrete (2005), American Concrete Institute ACI 318 Building Code Requirements for Structural Concrete (2005), American Concrete Institute A/E/C CAD Standards, V3.0 (or newer) available online at:

https://cadbim.usace.army.mil/default.aspx?p=s&t=13&i=4 ASTM - American Society for Testing and Materials UFC 4-010-01, Design: Minimum DoD Antiterrorism Standards for Buildings, 22 Jan 2007 https://cadbim.usace.army.mil/default.aspx?p=s&t=13&i=4

Section 01 10 15 - Page 2

1.6.2 AED DESIGN REQUIREMENTS DOCUMENTS

Unless specifically stated herein, the AED-N Standard Design Requirements (latest version) shall be adhered to in this Contract. These documents are available from the AED-N website located at:

http://www.aed.usace.army.mil/engineeringtop2010.asp

These documents shall be used as the basis for design and construction, and for selecting options within the United Facilities Guide Specifications (UFGS). When provided, it’s the Contractor’s option to use either the specifications contained in the AED-N Standard Design Requirements, or to adapt the UFGS specifications to match the requirements provided in the AED-N Standard Design Requirements. Site or project specific data and requirements in the AED-N Standard Design Requirements shall supersede UFGS language where there are differing criteria which must be evaluated and selected.

2.0 CIVIL REQUIREMENTS

The project includes furnishing all materials, equipment and labor for constructing electrical, water, communication, wastewater treatment and storm sewer service lines, as applicable, and connecting to the existing utility networks.

2.1 ENVIRONMENTAL PROTECTION

The Contractor shall comply with all requirements of Section 01 57 20 ENVIRONMENTAL PROTECTION.

2.2 SITE DEVELOPMENT

2.2.1 DEMOLITION

a. Demolition shall include clearing and grubbing of the site, and the removal of all existing structures, foundations, pavements, and utilities. All refuse and debris shall be promptly and properly disposed of off-site.

b. Holes and depressions shall be backfilled and compacted in lifts not to exceed 200 mm in height unless specified otherwise. Fill materials shall be composed of satisfactory soils or aggregates defined in ASTM D 2487 as GW, GP, GM, SP, SM, and SW. Minimum soil compaction shall be 95 percent of maximum density as defined in ASTM D 1557.

c. Scrap metal shall become the property of the Host Government. The scrap metal shall be moved to an area away from the site perimeter, or areas of ongoing site work, as directed by the Contracting Officer’s Representative, and left for the Host Government to remove and/or salvage. Demolished fencing and concertina wire shall be neatly rolled up for reuse by the Host Government. Demolished fence posts and outriggers shall be neatly stockpiled for reuse by the Host Government.

2.2.2 SITE GRADING

a. The Contractor shall provide all necessary site grading to insure that no areas will be flooded due to a rainfall of a 10-year frequency. Drainage of the area shall be compatible with the existing terrain.

Building floor elevations shall be a minimum 150mm above finished grade. Grade shall slope away from all sides of the buildings at a minimum of 3% for 3 meters. Protect all facilities from flood waters originating offsite, as based on a rainfall for a 25-year frequency event.

b. Rainfall data utilized for hydrology calculations shall be obtained from official meteorological records collected in Afghanistan. National agencies may be consulted for data. In the absence of site specific data, intensity-duration-frequency curves contained in the AED-N Standard Design Requirements – Hydrology (latest edition) shall be used. These curves shall be developed by extrapolating the rainfall intensity information from the stations in closest proximity to the project.

Under no circumstances will relationships developed by extrapolation from foreign countries be used for hydrologic studies.

http://www.aed.usace.army.mil/engineeringtop2010.asp

Section 01 10 15 - Page 3

2.3 EARTHWORK AND FOUNDATION PREPARATION

2.3.1 SATISFACTORY MATERIALS

Any materials classified by ASTM D 2487 as GW, GW-GM, GW-GC, SW, SW-SM, or SW-SC and free of debris, roots, wood, scrap material, vegetation, refuse, soft unsound particles, or objectionable materials.

Unless specified otherwise, the maximum particle diameter shall be one-half the lift thickness at the intended location.

2.3.2 UNSATISFACTORY MATERIALS

Any materials which do not comply with the requirements set forth in the Satisfactory Materials paragraph.

Unsatisfactory materials also include man-made fills, trash, refuse, or backfills from previous construction;

and materials classified as satisfactory which contains root and other organic matter, frozen material, and stones larger than 75mm. The Contracting Officer shall be immediately notified of any unsatisfactory materials.

2.3.3 CLEARING & GRUBBING

Unless indicated otherwise, remove tress, stumps, logs, shrubs, brush and vegetation, and other items that would interfere with construction operations within lines 1.5 meters outside of the building and structure line. Remove stumps entirely. Grub out matted roots and roots over 50mm in diameter to at least 460mm below existing surface.

2.3.4 EXCAVATION & COMPACTION OF FILL

a. Excavate to contours, elevation, and dimensions indicated. Reuse excavated materials that meet the specified requirements for the material type required at the intended location. Keep excavations free from water. Excavate soil disturbed or weakened by Contractor’s operations, soils softened or made unsuitable for subsequent construction due to exposure to weather. Excavations below indicated depths will not be permitted except to remove unsatisfactory material. Unsatisfactory material encountered below the grades shown shall be removed as directed. Refill with satisfactory material and compact to at least 95 percent of the maximum dry density, as determined by the Modified Proctor laboratory procedure. ASTM D 1557 shall be used for producing the Modified Proctor moisture-density curve, unless the soil to be compacted includes more than 30% retained on the 19 mm (3/4") sieve. In this case, the Contractor shall replace the ASTM D 1557 laboratory compaction procedure with AASHTO T 180, Method D, corrected with AASHTO T 224.

b. During compaction, the moisture content of the soil shall be within 1.5 percent of the optimum moisture content, as determined by the Modified Proctor laboratory procedure. The thickness of compacted lifts shall not exceed 15 cm and the dry density of each compacted lift shall be tested by sand cone (ASTM D 1556). Density tests shall be performed at a frequency of not less than one test for each 200 square meters and not less than two tests per compacted lift.

2.4 FORCE PROTECTION

2.4.1 PERIMETER WALLS

The Interlocking Alaska T-Walls will be constructed of the STANDARD size as shown in Appendix “J”.

The T-walls shall have flanges which give it the ability to overlap/interlock with anther T-Wall to create a continuous wall that is straight and flush.

2.4.2 OUTRIGGERS

Outrigger supporting arms shall be “U” shaped with metal “C-wire” support brackets (40 mm tubing), securely embedded 50 mm into the sides of the wall. Posts shall conform to ASTM F 1083, Pipe, Steel, Hot Dipped Zinc Coated (Galvanized) Welded. Outriggers shall be spaced a maximum of 3000 mm on center.

Section 01 10 15 - Page 4

2.4.3 REINFORCED BARB TAPE

Reinforced barbed tape shall be 600 mm diameter concertina style coil consisting of 31 loops. Each loop shall consist of 19 barb clusters per loop. Adjacent coils loops shall be alternately clipped together at three points about the circumference to produce the concertina effect upon deployment. Spacing between attachments points when deployed shall be 400 mm. The reinforced barbed tape shall be fabricated from 430 series stainless steel with hardness range of Rockwell (30N) 37-45 conforming to the requirements of ASTM A 176. Each barb shall be a minimum of 30mm in length, in groups of 4, spaced on 100 mm centers. The stainless steel core wire shall have a 2.5 mm diameter with a minimum tensile strength of 895 MPa. Sixteen gauge stainless steel twistable wire ties shall be used for attaching the barbed tape to the barbed wire. The reinforced barbed tape shall be equivalent to NSN: 5660-01-457- 9852.

2.4.4 SNIPER SCREEN

Sniper screen material will be ultraviolet light resistant and guaranteed against sunlight degradation for five years. Sniper screen material shall have 90% visibility blockage. Material will allow wind to blow through, without stretching the material, or distorting the frame. Sniper screen material will be fastened to standard galvanized fencing (conforming to ASTM F 1083, Pipe, Steel, Hot Dipped Zinc Coated (Galvanized) Welded), mounted to a rigid frame. The frame shall be securely embedded into the top of the wall. Frame components shall conform to ASTM F 1083, Steel Pipe, Hot Dipped Zinc Coated (Galvanized Welded). See Appendix “K – Sniper Screen.”

- END OF SECTION -

Section 01 32 17 - Page 1

SECTION 01 32 17

NETWORK ANALYSIS SCHEDULE

1 GENERAL

1.1 DESCRIPTION

The network analysis schedule (NAS) shall consist of the network analysis schedule (diagram) and associated reports. The scheduling of all procurement and construction shall be the responsibility of the Contractor. All procurement and construction activities will be integrated in a single schedule. The schedule will start at Contract Award and end at Contract Completion. The schedule may extend beyond Contract Completion, for activities such as demobilization, with the approval of the Contracting Officer’s Representative (COR). The contractual period of performance, from Notice to Proceed (NTP) to Contract Completion will be shown as a hammock under Contract Milestones.

The approved NAS constitutes the baseline schedule and represents the contractor’s plan for executing the project. The schedule will be updated monthly to show current status. The monthly updates will be used to measure work progress, aid in the evaluation of requests for time extensions, and to provide the basis of all progress payments. All progress payment amounts will equal the earned values calculated in the monthly NAS updates.

For consistency, when scheduling software terminology is used in this specification, the terms in Oracle’s Primavera scheduling programs are used. Primavera Project Planner, P3, and Primavera P6 are registered trademarks or service marks of Oracle. Adobe and Acrobat are registered trademarks of Adobe Systems Incorporated.

1.2 SUBMITTALS

Government approval is required for submittals with a "G" designation. Submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. The following will be submitted with Transmittal Form (ENG Form 4025) in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Baseline Network Analysis Schedule; G, RO

Project Execution Plan; G, RO

Monthly Network Analysis Schedule Updates; G, RO

Submit with Monthly Pay Requests

1.3 SCHEDULE ACCEPTANCE

Review comments made by the Government on the Contractor's schedules will not relieve the Contractor from compliance with the requirements of the Contract Documents. The Contractor is responsible for scheduling, sequencing, and prosecuting the Work to comply with the requirements of the Contract Documents. The Government will review the schedule for compliance with the contract

Section 01 32 17 - Page 2

(including contractual milestones and scope), cost loading and cost distribution, schedule organization and activity coding, logic, durations, and general conformance with established scheduling concepts and acceptable industry standards.

1.3.1 SCHEDULE ACCEPTANCE PRIOR TO START OF WORK

The Baseline NAS described in paragraph 1.7.2 Baseline Network Analysis Schedule must be accepted by the Government before the Contractor will be allowed to request progress payments except for DBA as noted below in 1.3.2.

1.3.2 ACCEPTANCE

a. After the Baseline NAS is accepted by the COR, it will be used by the Contractor for planning, organizing, and directing the work, reporting progress, and to support pay requests. The schedule will be updated monthly by the Contractor to reflect the current status of the work and will be submitted with the progress pay request. Processing pay requests is conditional upon receipt and acceptance of the Baseline NAS and accurate updated schedules accompanying the pay requests.

Only DBA insurance will be paid prior to acceptance of the Baseline NAS.

b. The Baseline NAS and subsequent schedule updates will be considered to be the Contractor's certification that the submitted schedule meets all of the requirements of the Contract Documents, represents the Contractor work plan, accurately reflects the work that has been accomplished, and the sequence in which it was performed.

1.4 SOFTWARE

The scheduling software utilized by the Government on this project will be Oracle’s Primavera P3, Primavera P6 or the most current version of Primavera. Notwithstanding any other provisions in the contract, schedules submitted for this project must be prepared using one of these programs. The program selected by the contractor will be used for the duration of the contract. The Contractor shall provide electronic files saved in compressed backup format (.prx or .xer) with all schedule submittals. If P6 (or newer) is used, the Contractor must provide the version number and a “.plf” file for each report.

Submission of data from another software system where data conversion techniques or software is used to import into Primavera's scheduling software is not acceptable and will be cause for rejection of the submitted schedule.

1.5 QUALIFICATIONS

The Contractor shall assign a Scheduler based in Afghanistan who will be responsible for the development, preparation, and maintenance of an accurate, computerized Network Analysis Schedule.

The Scheduler shall perform on-site coordination, attend project meetings, prepare reports and perform updates as required to support the project. The Scheduler shall have previously developed, created and maintained Primavera schedules for at least two projects similar in size and complexity to this contract.

A resume outlining the qualifications of the Scheduler shall be submitted for acceptance to the COR. If at a later date, the COR considers the Contractor's Scheduler to be incompetent or objectionable, the Contractor will propose a new Scheduler who meets the qualification requirements. Payments will not be processed until an acceptable Scheduler is assigned.

1.6 BASELINE NETWORK ANALYSIS SCHEDULE

Section 01 32 17 - Page 3

1.6.1 STRUCTURE

a. The NAS shall consist of a cost loaded CPM network displayed as time scaled bar charts supported by specified tabular and graphical reports. Sample standard reports are included in this section. The NAS will show the order and interdependence of activities and the sequence in which the work is planned to be accomplished. The basic concept of the network will be followed to show how the start and/ or finish of a given activity is dependent on the execution of preceding activities and how it restrains succeeding activities. Activity durations shall not be resource driven; activities shall not have date constraints, and shall start and finish according to network logic. Diagrams shall be organized with a four or five level project breakdown structure, sorted by Early Start and Early Finish Dates and will show a continuous flow from left to right. With the exception of the NTP Acknowledged and Contract Completion milestones, every activity must have predecessor and successor ties and every finish must have a successor. Activities with only start-to-start successor relationships will not be allowed. Activities in an accepted schedule may not be renamed or renumbered. The critical path is the longest path through the network; critical path activities shall be shown in red. Critical activities are defined as having zero or less days of Total Float. Near critical activities will be defined as having Total Float in the range of 1 to 14 calendar days. Barcharts shall be submitted formatted for 11” x 17” sheets.

b. The following information will be shown for each activity:

1. Activity ID

2. Activity Description

3. Original Duration in Work Days

4. Remaining Duration (schedule update reports only)

5. Percent Complete (schedule update reports only)

6. Early Start Date

7. Early Finish Date

8. Total Float

9. Budgeted Cost

10. Baseline Start Variance (schedule update reports only)

11. Baseline Finish Variance (schedule update reports only)

1.6.2 ACTIVITY PROPERTIES AND LEVEL OF DETAIL

Activity numberings shall be assigned so that, in general, predecessor activity numbers are smaller numerically than the successor activity numbers; this will aid in finding pay and schedule activities in RMS reports as they are sorted by activity ID. Skip numbering shall be used on the network to allow insertion of additional activities for contract modifications and logic changes.

1.6.2.1 GOVERNMENT ACTIVITIES

a. All Government activities shall be clearly identified in the schedule by including “AED” in the activity description and assigning the value “GOVT” to the activity code in RESP.

b. Government activities include, but are not limited to:

1. Government approved submittal reviews;

2. Government conducted inspections/tests;

3. Environmental permit approvals;

Section 01 32 17 - Page 4

4. Utility outages;

5. Notice(s) to Proceed (including Notices to Proceed for each Fast-Track Phase as indicated in other sections of this specification and as directed by the COR); and

6. Delivery of Government Furnished Material/Equipment.

c. Show activities indicating Government furnished materials and equipment utilizing delivery dates indicated in "FAR 52.245-2, Government Property (Fixed-Price Contracts).” Government activities will use a 7-day calendar (i.e. one with no non-work days).

d. Unless otherwise specified in the Contract, Government review/approval activities shall be assigned a duration of 14 calendar days.

1.6.2.2 CONSTRUCTION QUALITY MANAGEMENT (CQM) ACTIVITIES

All activities will have a Definable Feature of Work (FOW) as identified in the Contractor's Quality Control Plan. The FOW will be entered in the FOW activity code as defined in the SDEF specification.

1.6.2.3 ACTIVITY BANDS

a. The schedule shall be organized to at least three (3) levels. Larger and / or more complicated projects shall require additional levels as necessary. The levels shall be defined by the activity codes listed in the order indicated below:

1. PHAS;

2. AREA;

3. LVL3;

4. LVL4;

5. LVL5.

b. The first level, PHASE, shall be comprised of the following bands:

1. MILESTONES

This band contains the Contract milestones. If the Contractor includes other project milestones, contract milestones and project milestones will be shown as separate bands below

MILESTONES.

2. PRE-CONSTRUCTION

Included in this band are pre-construction meetings, submittals, and DAB Insurance. Pre-construction submittals will be shown as a separate band under PRE-CONSTRUCTION.

3. PROCUREMENT

This band contains tasks related to the procurement of installed material or equipment including but not limited to material submittal preparation, submittal and approval, fabrication, delivery, extra stock, special tools, O&M manuals, notification of Government Furnished Material/Equipment delivery requirement. As a minimum, separate procurement activities will be provided for every specification section. Submittal approval activities shall be logically tied to associated procurement, delivery, and/or construction activities. If the contractor requires payment upon delivery for materials or equipment, i.e. “stored materials”, a one day activity must succeed the delivery activity. The activity description should be “Stored Materials: name of

Section 01 32 17 - Page 5 materials or equipment”. The activity will carry the documented cost of the materials or equipment and will be stated as actual only after review and approval of the supporting documentation by the COR. Payment for stored materials if allowed by the contract is subject to approval by the COR and must be requested in writing prior to submittal of the baseline schedule. If the Government's action on any submittal is "Disapproved" or "Revise and Resubmit", a new series of Submittal Activities will be inserted into the schedule. Predecessor for the new submittal preparation activity will be the original approval activity and the successor will be the fabrication/deliver activity for the equipment or material.

4. CONSTRUCTION

This band will have as many subordinate bands as are required to provide a logical organization of construction work. These bands will contain all construction activities including but not limited to: mobilization; installation of temporary facilities; testing and inspection of installed work; start-up and testing of equipment; commissioning of building and related systems; and scheduling of specified manufacturer's representatives. No construction activity shall have a duration greater than 20 working days. Construction activities will be driven by calendars that reflect all scheduled non-work days (i.e. Fridays, official Afghan holidays and severe weather days as listed in Section 01 35 13 SPECIAL PROJECTS REQUIREMENTS of the Contract.)

5. CONTRACT CLOSEOUT

This band will have two or more subordinate bands to provide a logical organization of the closeout work. These bands will contain all closeout activities including but not limited to Punch Out Inspection, Pre-Final Inspection, Final Acceptance Inspection, final clean-up. as-built drawings, O&M manuals, training, and demobilization.

1.6.2.4 MILESTONES

The NAS will include milestones for the start of the project; any contractual interim start and finish dates, Contract Completion date, and other significant milestones. Only Contract Milestones will be recognized by the Government.

1. Contract Award

The schedule shall start with Contract Award. This will be shown as a start milestone with a mandatory start constraint equal to the actual Award Date.

2. NTP Acknowledged

NTP Acknowledged will be shown as a start milestone with a start-no-earlier-than constraint date equal to the date indicated in RMS.

3. Contract Duration

This will be shown as a hammock between NTP and Contract Completion. The duration of this hammock shall be equal to the Period of Performance indicated in RMS.

4. Contract Complete

The last activity in the schedule will be the Contract Complete milestone. This milestone will have a finish-no-later-than constraint date equal to the Contract Required Completion date in

RMS.

Section 01 32 17 - Page 6

1.6.2.5 MANDATORY ACTIVITIES

The following activities, and the procurement activities described in 1.6.2.1d, when applicable, shall be listed as separate activities:

1. Submission, review and approval of the demining plan and required demining activities through receipt of the certificate.

2. Submission and approval of the accident prevention plan.

3. Submission and approval of the security plan.

4. Submission and approval of the contractor quality control plan.

5. Submission and approval of the area use plan.

6. Mobilization / Demobilization.

7. Submission and approval of 1354 data and installed equipment lists.

8. Controls testing plan.

9. Controls testing.

10. Performance Verification testing.

11. Other systems testing, if required.

12. Pre-final inspection.

13. Correction of punch list from pre-final inspection.

14. Final inspection.

1.6.2.6 ACTIVITY NUMBER (ID) AND DESCRIPTION

a. Activity Numbers

Activity numbers shall consist of no more than ten (10) alphanumeric characters beginning with a letter. Only letters and numbers will be used. Activities must be numbered in ascending order from start to finish of the project.

b. Activity ID Codes

The Contractor shall submit the alphanumeric coding scheme for Activity Numbering that shall be used throughout the project. Activity ID Codes may be used to create a work breakdown structure (WBS). Four Activity ID fields are allowed in P3; user defined fields may be used in P6. The coding dictionary shall include the value and description of each code. Once accepted, the coding scheme will be used for the duration of the project.

c. Activity Description

Activity descriptions shall not exceed thirty (30) characters in length as limited by RMS. Each activity shall have a narrative description consisting of:

1. LOCATION;

(e.g. Building 1, 3rd floor, northeast quadrant, basement – abbreviate as necessary)

2. VERB; and

(e.g. form, pour, excavate),

3. OBJECT

(e.g. slab, footing, under floor plumbing).

1.6.2.7 ACTIVITY CODE DICTIONARY AND VALUES

Section 01 32 17 - Page 7

a. The Contractor shall use the activity coding structure defined in USACE Regulation ER 1-1-11 Standard Data Exchange Format (SDEF). The use of this exact structure is mandatory, even if some fields are not used. The SDEF fields may be used only for the purpose for which they are intended.

The characters remaining after the SDEF codes are limited to eight in Primavera P3. These activity codes may be used for additional PBS levels and price proposal line items. The codes will have values assigned that will allow the scheduling program to sort, select, group and organize the activities in the schedule. Activity codes are used to:

1. Group and summarize project activities in a hierarchical structure, in the same way as a project breakdown structure (PBS), to facilitate updating and analysis of the schedule;

2. Group and summarize activities and related costs by CLIN and Price Proposal Schedule Line Item;

3. and select and sort activities to create ad hoc views and reports.

b. Activity codes for Primavera version P6 or newer must be defined as “Project” type and not “Global” or “EPS.”

1.6.2.8 COST AND RESOURCE LOADING

a. Cost Loading Activities:

1. Payment for design work will be made after a design submittal is approved. The cost of the design submittal will be applied to a one day “Design Approved” task after the AED approval activity.

2. Payment for mobilization and demobilization shall be paid according to the approved CLIN amount for these items. Unless specified otherwise in the contract, then the amount shall be split 60 percent for mobilization and 40 percent for demobilization and each of these costs applied to these separate cost loaded activities.

3. The cost of installed materials and equipment will be included in the appropriate construction activities except as allowed by the contract and where the Contract Officer (KO) agrees in advance to payment for stored materials.

4. If payment is allowed by the KO for stored materials, the cost of the stored materials will be applied to a one day “Stored Materials Accepted” activity after the delivery activity.

5. Unless assigned a CLIN, indirect costs such as management, supervision, security, overhead, G&A and profit will be included in each activity budget. The total of all cost loaded activities shall equal the value of the contract.

6. Activity budgets shall be indicated in whole dollars if the Contract and CLIN costs are indicated in whole dollars. If the Contract contains values to two decimal places, the activity budgets shall be rounded to whole dollars and the correction for rounding assigned to one activity per CLIN.

Cost shall be assigned to activities as a resource as described in the QCS requirements for SDEF file transfer.

7. In P6, cost must be entered as a resource not an expense. The cost resource must be set up with a non-labor resource type, zero default units/time, zero max units/time and zero price/unit. The two check boxes under Resource – Details – Profile must be unchecked. Only budgeted cost will be entered for the cost resource.

8. Hammocks (summary bars) will not be cost loaded.

Section 01 32 17 - Page 8

9. CLINs and resources will not be entered for activities with no budget.

b. Cost Loading Milestones

Milestone activities may not be cost loaded. A one day task should be used in instead of a cost loaded milestone such as Design Approved or Stored Materials Accepted.

c. Contract Line Item Number (CLIN)

As described in Cost Loading, cost shall be assigned to every task type activity. Every activity shall also be assigned to a CLIN. All cost and earned value reports will be grouped by Project and CLIN with sub groups as appropriate. Group totals will be shown for Project and CLIN.

d. Key Quantities

Key quantities will be included as a resource for all cost loaded construction activities. Resource units of measure and cost per unit will be set up in the resources table. Key quantity resources will be non-driving

e. Labor Resource Loading

As part of the Baseline Schedule development each construction activity shall have an estimate of the number of workers per day by trade, hours per day by trade and total expected hours used by trade during the execution of the activity. If no workers are required for an activity, then the activity shall be identified as using zero workers per day. All labor resources loaded into the schedule shall be non-driving and will not be used to calculate activity cost or duration. Resource leveling shall not be used. Actual labor resource expended on an activity will be recorded in the monthly updated schedules and will coincide with entries made in the Daily Reports.

f. Price Units

In P6 quantity and labor resources must be set up with price/unit equal to zero. Only units (no cost) will be entered for these resources.

1.6.2.9 CALENDARS

a. In P6, calendars must be set up as Project (not Global) calendars.

b. Three calendars will be used in preparing the schedule:

1. 7 day week, no weekends or holidays, and no weather (7 Day Calendar)

This calendar is used for any activity whose duration is measured in consecutive calendar days.

These activities are mainly in the design and procurement phases. Examples are AED design review, fabricate & deliver.

2. 6 day week, with non work weekend days, and public holidays, no weather (Standard Calendar)

This calendar is used for construction activities which are not affected by severe weather conditions. Examples are all interior work and above ground structural work which is not temperature sensitive such as structural steel erection. Some activities may require interior heating in cold weather for example, painting and plastering.

3. 6 day week with public holidays and severe weather days as listed in Section 01 32 13 SPECIAL PROJECT REQUIREMENTS (Weather Calendar)

Section 01 32 17 - Page 9

This calendar is used for construction activities which cannot or will not be performed in severe weather conditions (such precipitation, high or low temperature, wind), such as earthwork, excavation, compaction, concrete work, exterior plastering.

c. The total number of non work days for any given month will not…