A21 - W912PM23B0007-RTA1-SPECS-FY24MOTSU-Maint-Dredging.pdf

Solicitation No. W912PM23B0007 Contract No. W912PM22XXXXXX

MAINTENANCE DREDGING,

FY24 MILITARY OCEAN

TERMINAL (MOTSU)

SUNNY POINT

BRUNSWICK COUNTY,

NORTH CAROLINA

This project was designed by the Wilmington District of the U.S. Army Corps of Engineers. The initials or signatures and registration designations of individuals appear on these project documents within the scope of their employment as required by ER 1110-1-8152.

RTA SPECIFICATIONS

22-JUNE-2023

FY24 MOTSU Maintenance Dredging MOTSUDREDGING24

W912PM23B0007 RTA

PROJECT TABLE OF CONTENTS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 10 00.10 38 1/17 SUPPLEMENTARY SPECIAL CONTRACT

REQUIREMENTS

01 32 01.00 10 02/15 PROJECT PROGRESS SCHEDULE

01 33 00 08/18, CHG 4: 02/21 SUBMITTAL PROCEDURES

01 35 26 11/20, CHG 3: 02/22 GOVERNMENTAL DREDGING SAFETY

REQUIREMENTS

01 42 00 02/19 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 11/16, CHG 2: 11/21 QUALITY CONTROL

01 45 00.15 10 11/16, CHG 2: 08/19 RESIDENT MANAGEMENT SYSTEM CONTRACTOR

MODE (RMS CM)

01 50 00 11/20, CHG 2: 08/22 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 57 19 08/22 TEMPORARY ENVIRONMENTAL CONTROLS

DI VI SI ON 35 - WATERWAY AND MARI NE CONSTRUCTI ON

35 20 23 08/20 DREDGING

35 20 23.13 02/22 NATIONAL DREDGING QUALITY MANAGEMENT

PROGRAM - SCOW MONITORING PROFILE

35 20 23.33 02/22 NATIONAL DREDGING QUALITY MANAGEMENT

PROGRAM - PIPELINE HYDRAULIC DREDGE

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 10 00.10 38

SUPPLEMENTARY SPECIAL CONTRACT REQUIREMENTS

1/17

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 EMPLOYEE IDENTIFICATION AND SECURITY

1.3.1 Background Checks

1.3.2 Employee Identification

1.3.3 Employee Information Update

1.3.4 Vehicle Usage

1.3.5 Protection of Plant and Personnel

1.3.6 Coordination Meeting

1.3.7 Security Training

1.3.8 Completion of Security Training

1.4 PERFORMANCE AND PAYMENT BONDS

1.5 RETAINAGE FOR UNTIMELY SUBMISSION OF SUBCONTRACTING REPORTS

1.6 WORK IN QUARANTINED AREA

1.7 PARTNERING

1.8 COORDINATION WITH OTHER CONTRACTORS

PART 2 PRODUCTS

PART 3 EXECUTION

ATTACHMENTS:

Attachment 1 - IWATCH Training and Active Shooter Training

Attachment 2 - MOTSU Safety and Security Requirements

-- End of Section Table of Contents --

SECTION 01 10 00.10 38 Page 1

SECTION 01 10 00.10 38

SUPPLEMENTARY SPECIAL CONTRACT REQUIREMENTS

1/17

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1110-1-5 Plant Pest Quarantined Areas and Foreign Soil Samples

1.2 SUBMITTALS

Government approval is required for submittals with a "GA" designation;

submittals not having a "GA" designation are for information only. When used, a designation following the "GA" designation identifies the office that will review the submittal for the Government. The following shall be submitted in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of Subcontractors

Progress Chart; GA

Quality Control Plan; GA

Accident Prevention Plan (APP); G

Environmental Protection Plan; G

SD-07 Certificates

Certificate of Insurance

Completion of Corps CQC Course

Letter Appointing Superintendent

1.3 EMPLOYEE IDENTIFICATION AND SECURITY

1.3.1 Background Checks

Contractors are responsible for submitting NCIC form for all employees to the Contracting Officer, or his/her representative. The Contracting Officer, or his/her representative will then submit these forms to MOTSU Security for clearance. The clearance process will require at least 5 days. The Contractor shall start this process within 2 days after award.

The background checks will be provided to the Chief, Installation Security Activity, who will issue identification badges to employees whose

SECTION 01 10 00.10 38 Page 2 clearance meets requirements for admission. MOTSU Security point of contact is Ms. Sabrina Cramer, (910) 457-8936. The Contractor shall comply with the applicable provisions of Safety and Occupational Health Requirements, with exception of accident reporting which shall be in accordance with contract specifications.

1.3.2 Employee Identification

Within 2 days after award, the Contractor shall furnish the Contracting Officer, names, copy of driver's license, and vehicular tag numbers of each employee that will be working on this contract. The Contractor shall require employees to display identification when requested.

1.3.3 Employee Information Update

If, there are any changes in the information required by the previous subparagraph, prior to completion of work, the Contractor shall promptly furnish updated information to the Contracting Officer.

1.3.4 Vehicle Usage

The Contractor's personnel shall not drive privately owned vehicles to the work site without the approval of the Contracting Officer. The Contractor shall provide transportation to and from the work site.

1.3.5 Protection of Plant and Personnel

It will be the responsibility of the Contractor to take those measures which he/she deems necessary to protect his/her plant and personnel from harm prior to beginning work.However, as MOTSU facilities are directly associated with explosive operations and storage, there are inherent risks associated with working in an explosive hazard area. For specific procedures and precautions applicable to working on the MOTSU installation, see Attachment 2 - MOTSU SAFETY AND SECURITY REQUIREMENTS.

1.3.6 Coordination Meeting

The Contracting Officer will arrange an initial coordination meeting between the Contractor and MOTSU which will be held before the Contractor begins work. When work begins, the Contractor shall coordinate all activities with the designated MOTSU personnel on a day to day basis.

1.3.7 Security Training

Contractor employees assigned to perform work under this contract at MOTSU shall attend/complete the following training within thirty (30) days of contract start, when applicable, as prescribed by DOD, Army and SDDC Regulations: Employee Initial Security Briefing, Operations Security (OPSEC), Threat Awareness and Reporting Program (TARP), DOD Antiterrorism Level 1 Training, Active Shooter, iWATCH Training, and Workplace Violence Training. This also includes Information Assurance (IA) Training required for specific computing platforms and applications. All Security training, to include Annual Security Awareness Training, is required annually.

Training will be facilitated by the MOTSU Security Specialists.

NOTE:

iWATCH Training and Active Shooter Training are the minimum security training requirements. MOTSU will provide literature to contractor for self-performance of training. See Attachment 1 -

SECTION 01 10 00.10 38 Page 3

IWATCH Training and Active Shooter Training and Attachment 2 - MOTSU Safety and Security Requirements.

1.3.8 Completion of Security Training

Contractor employees will report training completion to the Contracting Officer or his/her authorized representative.

1.4 PERFORMANCE AND PAYMENT BONDS

Each bidder shall include his premiums for performance and payment bonds under the "Performance and Payment Bonds" contract line item of the Bidding Schedule. Payment to the Contractor therefore, shall not exceed the bid price and shall be made in accordance with the Contract Clause entitled "PAYMENTS UNDER FIXED-PRICE CONSTRUCTION CONTRACTS." Any additional amount bid in excess of the actual bond premium will be included in the final pay estimate for this contract.

(End of Clause)

1.5 RETAINAGE FOR UNTIMELY SUBMISSION OF SUBCONTRACTING REPORTS

(a) In accordance with Contract Clause 52.219-9, Small Business Subcontracting Plan, and 52.219-16, Liquidated Damages - Subcontracting Plan, retainage will be withheld from progress payments in an amount sufficient to protect the Government's ability to assess liquidated damages in accordance with Clause 52.219-16 for the contractor's failure to timely submit Standard Form 294, Subcontracting Report for Individual Contracts, and Standard Form 295, Summary Subcontract Report, reports.

(b) The retainage will be determined in accordance with the following formula:

Total dollar amount for subcontracting to small business multiplied by percentage of actual progress on the contract shall be withheld from the next progress payment due after the Contractor fails to submit a required report. If one or more reports have been submitted before such failure, formula for determining the amount of retainage will be adjusted by deducting any amounts reported as subcontracted to small business from the total dollar amount proposed to be subcontracted and the difference multiplied by the percentage of actual progress.

(c) Subcontracting plans are not required--

(1) For contracts or contract modifications that will be performed entirely outside of any State, territory, or possession of the United States, the District of Columbia, and the Commonwealth of Puerto Rico; or

(2) For modifications to contracts that do not contain the clause 52.219-8, Utilization of Small Business Concerns and Small Disadvantaged Business Concerns (or equivalent prior DAR, FPR, or NASA clauses); e.g., contracts awarded before Pub. L. 95-507 and which are within the scope of the contract.

(End of Clause)

SECTION 01 10 00.10 38 Page 4

1.6 WORK IN QUARANTINED AREA

USACE and the U.S. Department of Agriculture (USDA) have a compliance agreement requiring measures to prevent the spread of certain plant pests that may be present in the soil (USACE ER 1110-1-5 ). Major portions of all southeastern states are in a quarantine area for such pests, including the imported fire ant. In addition, adjacent states to the north have introduced infestations resulting from movement of soil from infested southeastern states. The Contractor shall thoroughly clean all construction equipment and tools at the previous job site in a manner that ensures that these implements are free from residual soil, egg deposits from plant pests, noxious weeds, and plant seeds. Equipment shall be cleaned using water under pressure, and hand tools shall be thoroughly cleaned by brushing or other means to remove all soil. In addition, all construction equipment and hand tools used for this USACE contract shall be thoroughly cleaned by the Contractor before they are removed from this job site. The Contractor shall consult with the USDA jurisdictional office for additional cleaning requirements that may be necessary.

(End of Clause)

1.7 PARTNERING

In order to most effectively accomplish this contract, the Government proposes to form a cohesive partnership with the Contractor and its subcontractors. This partnership would strive to draw on the strengths of each organization in an effort to achieve a quality project done right the first time, within budget and on schedule. Integral to the partnership would be a joint Contractor/Government effort to settle any disputes that may arise without costly and time consuming litigation. To that end, a non-binding procedure such as the Alternate Dispute Resolution process could be developed and agreed upon by both parties when it is determined to be necessary. This partnership would be bilateral in make-up and participation will be totally voluntary. Any cost associated with developing this partnership will be agreed to by both parties and will be shared equally with no change in contract price.

(End of Clause)

1.8 COORDINATION WITH OTHER CONTRACTORS

Other Contractors may be working in the vicinity during the time period of this contract. The Contractor shall coordinate the contract operations with other Contractors in the area as needed to avoid conflicts and delays. Any potential delays due to conflicts with other contractors shall be reported to the Contracting Officer or his/her designated representative immediately.

(End of Clause)

PART 2 PRODUCTS

Not Used.

PART 3 EXECUTION

Not Used.

-- End of Section --

SECTION 01 10 00.10 38 Page 5

SECTION 01 10 00.10 38 Page 6

Attachment 1

IWATCH Training and Active Shooter Training

What is iWATCH ARMY?

iWATCH, iREPORT, i KEEP US SAFE (iWATCH ARMY} is a community program to help your neighborhood stay safe from terrorist activities.

You and your fellow Army community members can report behaviors and activities that make you feel uncomfortable and do not look right (suspicious behaviors).

iWATCH ARMY is a program and partnership between your community and your local law enforcement.

iWATCH ARMY asks you to report behavior and activities that are unusual or seem out of the ordinary.

Why Report These Behaviors and Activities?

It is your awareness reported to local law enforcement that can help predict and prevent attacks before they happen.

Since 9-11, we can and must work together to prevent future attacks.

It is always better to report suspicious behaviors than to refrain from doing so.

The iWATCH ARMY program is about behaviors and activities, not individuals.

ctivities Do I Report?

He~e.a.re e~amples of behaviors and act1v1t1es to report:

* People drawing or measuring important buildings.

* Strangers asking questions about securi1y forces or security proce9ures.

* A briefcase, suitcase, backpack or package left behind.

* Cars Of trucks left in No Parking zones in front of important buildings.

* Intruders found in secure areas.

* A person wearing clothes that are too big and bulky and/or too hot for the weather.

* Chemical smells or fumes that worry you.

* Questions about sensitive infor~ation such as building blueprints, security plans or VIP travel schedules without a right or need to know.

* Purchasing supplies or equipment that can be used to make bombs or weapons or purchasing uniforms without having the proper credentials.

Example Situations

"There's a chemical smell coming from my neighbor's apartment."

"I saw someone taking measure ments. I don't want to get them in trouble. What should I do?"

{This activity may be repeated at other locations and you may be reporting one piece of the puzzle.)

"Maybe someone just forgot their briefcase on the bus."

(Do not check it yourself It may be a test.)

/ saw someone watching our offices, and the next day my co-worker was asked a lot of questions about our building by someone else."

(Do not check it yourself It may be a test.)

Unsure what to do?

Let the experts decide!

Call: [emergency hotline number]

Call: [Military Police number]

Call: [local law enforcement number]

Important Places to Watch

* Unit Headquarters

* Installation access points

* Religious facilities

* Amusement parks

* Sports/entertainment venues

I * Recreation centers, fitness facilities

* Barracks, lodging facilities

* Mass g1therings-parades, fairs, etc.

* Schools, libraries, day care centers

* Hospitals

* Commissary, PX, gas station, bank

* Public transportation

Trust Your Instincts

We rely on our senses every day of our lives. If a behavior or activity makes you feel uncomfortable, report it!

Here are some examples of suspicious activities reported by concerned individuals that saved lives:

A video store clerk saw anti-American material on a DVD he was asked to copy. Police captured and arrested individuals planning an attack against a military installation.

If it doesn't LOOK right, report it!

A grandmother smelled bad odors from the neighboring apartment and noticed that the empty apartment was frequented by various people.

Police discovered a poison gas factory.

Ifit doesn't SMELL right, report it!

Residents were concerned with a person's threats of violence. Police captured and arrested a group planning a subway attack.

Ifit doesn't SOUND right, report it!

Wh~t Should I Report?

Give as many details as you can. Here is a checklist to help you.

1. The date and time.

2. Where it happened.

3. What r ou witnessed.

4. A descrription of who was involved

• Male or female?

• How tall?

• Buil~?

• Hair)color, skin color, age?

English speaking or another lang~age?

5. Was there a car? Note the license plate number.

6. Have you seen this activity in your neighfuorhood before?

Hbw Do I Report?

There are ~three] ways to make a report:

* Call [i~sert phone number]. An expe1 will answer the call and advise you.

* Call y~ur local military police station [phonf number] and make your repo1 to the desk officer.

* In an emergency call [local hotline]

All information lill be kept confidential. Information submitted will Ile carefully assessed and, if warranted, investigated by rained investigators. All information gathered and al investigative activity will be subject to strict policies designe to protect the privacy and civil liberties of American citize · s while protecting our Nation from terrorism

Attachment 2

MOTSU SAFETY AND SECURITY

REQUIREMENTS

SAFETY (EXPLOSIVE HAZARD/RISK) REQUIREMENTS

1. Explosive Hazard/Risk

1.1 Acknowledgment of the potential risk associated with the operations being undertaken by the Army, the contractor and contractor employees. MOTSU facilities are directly associated with explosive operations and storage. Additionally, explosive munitions are occasionally loaded and unloaded off vessels. As a contractor performing work on the installation, it is imperative that you are aware of the associated hazards and know the precautions to take. While contractor personnel are on the installation, they will be exposed to potential explosive hazards. If an accidental detonation on the installation were to occur while contractor personnel and/or equipment are present, the following consequences are possible, depending on variables such as amount of explosives involved and the distance from the explosion:

a. Personnel may be seriously injured or killed by blast, debris, or impact against hard surfaces.

b. Vehicles may be overturned, crushed, or damaged by the blast or debris.

1.2 Evacuation requirements in the event of an emergency in/near/around the contractors work area which may include but is not limited to weather and/or operational emergencies. You will be notified as applicable. When MOTSU’s lightning warning systems (LWS) shows lightning within various designated radii (i.e. 25 to 5 mile radius), MOTSU personnel will announce on the radio, cell phone or in-person the status and whether evacuation is required. The MOTSU procedure for terminating ammunition operations during a thunderstorm can be found in the most recent revision of MOTSU SOP No. W90GAD-0000-T-301. A copy of the Section entitled “PROCEDURES FOR

TERMINATING AMMUNITION OPERATIONS DURING A THUNDER STORM”

can be obtained from MOTSU.

1.3 If contractor personnel are instructed by the MOTSU warning systems to evacuate, immediately cease work, leave everything, and evacuate the area to a predetermined area.

1.4 If the contractor is performing maintenance dredging at MOTSU when an ammunition ship is present, this may require dredge plant and/or personnel to evacuate as well.

Dredge plant may be left in-place if it is secured and properly anchored. Once there, account for all personnel. If someone is missing, please contact the MOTSU Fire or Police Dept (910-457-8911) and inform them of the work location and the number of unaccounted personnel, if any.

1.5 When the “all clear” signal is given by MOTSU warning systems, contractor personnel may return and resume work.

1.6 When any “imminent danger” situation is discovered, immediately cease operations, withdraw personnel from the hazard and immediately notify MOTSU staff.

1.7 All contractor employees will be requested to execute an acknowledgement of the installation’s explosive hazard risk. The form will be provided to the contractor by

MOTSU Staff at the initial brief so the contractor can disseminate to each employee. The acknowledgements will be retained by the contractor.

SECURITY (PHYSICAL, PERSONNEL, INFORMATION, OPERATION, INDUSTRIAL

SECURITY, AND ANTITERRORISM / FORCE PROTECTION) REQUIREMENTS

1. Search, Inspection, and Seizure: All vehicles, personnel, and hand-carried items, entering or exiting any installation control point, or while on the installation, are subject to search and inspection and seizure of any prohibited item, at any time. Random, unannounced, and regular searches and inspections will be conducted. These searches and inspections are intended to assure prohibited articles are not introduced into, and government property is not removed from the installation or its facilities.

2. Parking: Parking of the Contractor’s vehicles shall be restricted to the area of work. The company name shall be prominently displayed on all construction vehicles parked where work is being accomplished.

3. Driver’s Licenses: All persons entering or working on MOTSU shall possess a valid Driver’s License or State issued Real ID Card.

4. Seatbelts: The use of seatbelts by all vehicle operators and passengers is mandatory on MOTSU. Vehicle operators caught not wearing seatbelts will lose their driving privileges, subject to laws governing Military and Civilian Employees.

5. Cell Phones: The use of cell phones while driving vehicles is prohibited on MOTSU, subject to laws governing Military and Civilian Employees.

6. Traffic Laws. The contractor and its employees shall comply with installation traffic regulations.

7. Key Control. The contractor shall establish in writing and implement methods of making sure all keys issued to the contractor by the Government are not lost or misplaced and are not used by unauthorized persons. This established plan shall be submitted to the Contracting Officer or his/her authorized representative in writing. The contractor shall not duplicate any keys issued by the Government.

7.1. The contractor shall immediately report to the Contracting Officer or his/her authorized representative occurrences of lost or duplicated keys.

7.2. In the event keys, other than master keys, are lost or duplicated, the contractor may be required, upon written direction of the Contracting Officer or his/her authorized representative, to re-key or replace the affected lock or locks without cost to the Government. The Government may, however, at its option, replace the affected lock or locks or perform re-keying and deduct the cost of such from the monthly payment due the contractor. In the event a master key is lost or duplicated, the Government shall replace all locks and keys for that system and the total cost deducted from the monthly payment due the Contractor.

7.3. The Contractor shall prohibit the use of keys, issued by the Government, by any persons other than the Contractor's employees and the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in performance of contract work requirements in those areas.

8. Lock Combinations: The contractor shall control access to all Government provided lock combinations to preclude unauthorized entry.

9. General Security Information: The overall classification of work associated with this contract is at the UNCLASSIFIED level. Personnel assigned to this contract require access to UNCLASSIFIED government systems, and/or require a Common Access Cards (CAC).

10. Personnel Clearance Level (PCL) / Investigation Requirements: Contractor employees must successfully complete a National Agency Check with Inquiries (NACI) resulting in favorable suitability for Public Trust eligibility. NACI investigations must be opened with fingerprint, name and criminal records checks returned favorably before contractors are cleared to begin work on the contract. Favorable NACI investigation results must be posted in the Joint Personnel Adjudication System (JPAS) before a Contractor is granted a CAC or have access to Government information systems. The Contractor and/or subcontractor(s) shall possess the capability to articulate well, speak and write fluently in the English Language, and comprehend the English Language.

10.1. NACI requests will be submitted to the MOTSU Security Specialist, via a Personnel Security Investigation Program (PSIP) form, for processing as soon as the employees are identified.

10.2. SDDC will only process NACI/Position of Trust investigations and will not complete any personnel security investigations for classified access. It is incumbent upon the contractor to have the appropriate investigations completed upon start of the contract.

11. Clearance / Investigation Validation Checks: Upon award of this contract, all names of contract employees supporting this contract will be submitted to the MOTSU Security Specialist, through the Contracting Officer or his/her authorized representative, for vetting in JPAS to ensure investigative requirements have been obtained before contract start date. List of employees will consist of Name, SSN, home address, and telephone number. If a contract member does not have the appropriate investigative requirement to support this contract, the employee will be denied the ability to work in support of this contract. Notification of this will be provided to the Contracting Officer or his/her authorized representative upon verification by the MOTSU Security Specialist.

12. MOTSU Badge: Upon notification by the MOTSU Security Specialist that contractor personnel meet the required investigative levels, personnel will be loaded in CVS with an expiration date on their CAC for the current period of performance.

13. Terminal Access: Contractor employees will comply with base access and control procedures. The Visitor Center personnel will conduct a National Crime Information Center

(NCIC) check on all personnel who request access to MOTSU. A MOTSU NCIC Consent form must be signed and submitted within at least seven (7) days of coming to the terminal. If there is nothing prohibiting the individual from working on the installation, they will be granted access.

The Visitor Center is available 0600 to 1400 Monday thru Friday; telephone number is (910) 457-8269 or 8766. POC is the Chief of Guards at (910) 457 8502.

14. Visit Authorization: Permanently assigned contractors at MOTSU will require electronic JPAS visit requests submitted to SMO Code: W6TCAA, POC block is the contract number and phone number block will include Contracting Officer or his/her authorized representative phone number and last name.

15. In/Out-Processing: Upon termination or completion of this contract, the contractor employee will surrender all Government supplies, materials, and equipment to the Contracting Officer or his/her authorized representative. In addition, the Contractor CAC and any security badges issued will be turned into the Contracting Officer or his/her authorized representative.

This will be accomplished on the last day of the contract or upon any termination/reassignment of a contract employee. The Contracting Officer or his/her authorized representative who obtains CAC and security badges due to short notice terminations or release of contract employees turn the CAC into the S-1 and all security badges into the MOTSU Visitor Center for final processing/out-processing.

16. Security Training: Contractor employees assigned to perform work under this contract at MOTSU shall attend/complete the following training within thirty (30) days of contract start, as prescribed by DOD, Army and SDDC Regulations: Employee Initial Security Briefing, Operations Security (OPSEC), Threat Awareness and Reporting Program (TARP), DOD Antiterrorism Level 1 Training, Active Shooter, iWATCH Training, and Workplace Violence Training. This also includes Information Assurance (IA) Training required for specific computing platforms and applications. Training will be facilitated by the MOTSU Security Specialists and provided via on-line training or applicable literature.

NOTE: iWATCH Training and Active Shooter Training are the minimum security training requirements. MOTSU will provide literature to contractor for self-performance of training.

16.1. Contractor employees will report training completion to the Contracting Officer or his/her authorized representative.

17. Security Permissions on DoD Systems: The Government shall ensure roles/privileges assigned to contract employees on the Government computing platforms are limited to those required for that individual’s performance of their assignments. These roles/privileges can be limited or revoked by the Government for any reason.

18. Security Compliance / Deviations: If the Government notifies the Contractor that the employment or the continued employment of any contractor employee is prejudicial to the interests or endangers the security of the United States of America, that person shall be removed and barred from the worksite.

18.1. Circumstances surrounding the removal of contract employees include security deviations/incidents and credible derogatory information received or uncovered on contract members during the course of the contractual period. The contract company shall make any changes necessary in the appointment(s).

18.2. Persons employed by Army contractors will report threat-related incidents, behavioral indicators, and other matters of Counter-Intelligence (CI) interest specified in AR 381-12, Chapter 3, to the Facility Security Officer, MOTSU Security, the nearest military CI Office, the Federal Bureau of Investigation, or the Defense Security Service.

18.3. Operations Security (OPSEC): All information furnished to the Contractor is to be used FOR OFFICIAL USE ONLY (FOUO). The Contractor is required to be aware of OPSEC requirements from SDDC. Information determined as FOUO or included as part of the OPSEC Essential Elements of Friendly Information (EEFI) is not to be released to the public.

19. FPCON Impact on Work Levels (US Installation Only): Contractors are not considered mission essential in this contract; therefore, access to the installation during increased force protection condition (FPCON) CHARLIE and DELTA is not authorized.

20. Security Regulation Compliance: The Contractor will be required to comply with all security regulations and directives as identified herein, and other security requirements located in this contract. The Contractor shall not divulge any financial, planning, programming, or budgeting information without the express consent of the Government as outlined in Operational Security (OPSEC) and Information Security regulations.

20.1. Safety and Security Regulation Guidance:

Department of Defense (DOD):

2000.16 (DOD Antiterrorism (AT) Standards)

5200.01 (DOD Information Security Program, 4 Vol’s) 5200.2-R (DOD Personnel Security Program) 5200.08-R (DOD Physical Security Program) 5220.22-M (National Industrial Security Program) 8500.1 (Information Assurance)

2000.12 (DOD Antiterrorism (AT) Program)

8500.2 (Information Assurance (IA) Implementation) DESR 6055.09, Defense Explosives Safety Regulation DOD regulations found at: http://www.dtic.mil/whs/directives/corres/pub1.html

Army:

AR 25-2 (Information Assurance) AR 380-5 (Department of the Army Information Security Program) AR 380-20 (Restricted Areas) AR 380-49 (Industrial Security Program) AR 380-67 (Personnel Security Program)

AR 381-12 (Threat Awareness and Reporting Program) AR 525-13 (Antiterrorism) AR 530-1 (Operations Security) AR 190-11 (Physical Security of AA&E) AR 190-13 (Army Physical Security Program) AR 385-10, The Army Safety Program DA PAM 385-64, U.S. Army Ammunition and Explosives Safety Standards DA PAM 385-30, Risk Management Army regulations found at: http://armypubs.army.mil/

SDDC:

SDDC Regulation 190-13 (SDDC Physical Security Program) SDDC Regulation 380-2 (SDDC Operations Security Program) SDDC Regulation 380-5 (SDDC Information Security Program)

MOTSU:

SOP NO: W90GAD-0000-T-301 (current version)

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT PROGRESS SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 PROJECT SCHEDULER QUALIFICATIONS

PART 2 PRODUCTS

2.1 SOFTWARE

2.1.1 Government Default Software

2.1.2 Contractor Software

2.1.2.1 Primavera

2.1.2.2 Other Than Primavera

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.2.1 Level of Detail Required

3.2.2 Activity Durations

3.2.3 Procurement Activities

3.2.4 Mandatory Tasks

3.2.5 Government Activities

3.2.6 Standard Activity Coding Dictionary

3.2.6.1 Workers Per Day (WRKP)

3.2.6.2 Area of Work Coding (AREA)

3.2.6.3 Modification Number (MODF)

3.2.6.4 Bid Item Coding (BIDI)

3.2.7 Contract Milestones and Constraints

3.2.7.1 Project Start Date Milestone and Constraint

3.2.7.2 End Project Finish Milestone and Constraint

3.2.7.3 Interim Completion Dates and Constraints

3.2.7.3.1 Start Phase

3.2.7.3.2 End Phase

3.2.8 Calendars

3.2.9 Open Ended Logic

3.2.10 Default Progress Data Disallowed

3.2.11 Out-of-Sequence Progress

3.2.12 Added and Deleted Activities

3.2.13 Original Durations

3.2.14 Leads, Lags, and Start to Finish Relationships

3.2.15 Retained Logic

3.2.16 Percent Complete

3.2.17 Remaining Duration

3.2.18 Early Completion Schedule and the Right to Finish Early

3.3 PROJECT SCHEDULE SUBMISSIONS

SECTION 01 32 01.00 10 Page 1

3.3.1 Initial Project Schedule Submission

3.3.2 Periodic Schedule Updates

3.4 SUBMISSION REQUIREMENTS

3.4.1 Data

3.4.2 Network Diagram

3.4.2.1 Continuous Flow

3.4.2.2 Project Milestone Dates

3.4.2.3 Critical Path

3.5 WEEKLY PROGRESS MEETINGS

3.6 REQUESTS FOR TIME EXTENSIONS

3.6.1 Justification of Delay

3.6.2 Time Extensions for Unusually Severe Weather

3.6.3 Time Impact Analysis (Prospective Analysis)

3.6.4 Fragmentary Network (Fragment)

3.6.5 Time Extension

3.6.6 Impact to Early Completion Schedule

3.7 FAILURE TO ACHIEVE PROGRESS

3.7.1 Artificially Improving Progress

3.7.2 Failure to Perform

3.7.3 Recovery Schedule

3.8 OWNERSHIP OF FLOAT

3.9 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

3.10 PRIMAVERA P6 MANDATORY REQUIREMENTS

SECTION 01 32 01.00 10 Page 2

SECTION 01 32 01.00 10

PROJECT PROGRESS SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

AACE INTERNATIONAL (AACE)

AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (1995) Administration -- Progress, Schedules, and Network Analysis Systems

1.2 SUBMITTALS

Government approval is required for submittals with a "G" designation.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Initial Project Schedule; G

Periodic Schedule Update; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

The Contractor shall designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The authorized representative must have a minimum of 2-years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. Representative must have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

The scheduling software utilized to produce and update the schedules required herein must be capable of meeting requirements of this specification.

SECTION 01 32 01.00 10 Page 3

2.1.1 Government Default Software

The Government intends to use Primavera P6 and/or Microsoft Project Professional 2016 (or later).

2.1.2 Contractor Software

Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required SDEF file must be created and supported by the software manufacturer.

2.1.2.1 Primavera

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.

2.1.2.2 Other Than Primavera

If the contractor chooses software other than Primavera P6 or Microsoft Project Professional 2016, that is compliant with this specification, the contractor must request permission from the Government to use the software prior to submission of associated submittals.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Pursuant to the Contract Clause FAR 52.236-15, SCHEDULES FOR CONSTRUCTION CONTRACTS, a project schedule as described in this paragraph PROGRESS SCHEDULE shall be prepared and submitted. The Contractor shall provide the project schedule in the Precedence Diagram Method (PDM) using the Standard Data Exchange Format (SDEF). The project schedule shall be used to measure progress of the work, to evaluate potential time extensions and to provide a basis for all progress payments. It shall be in sufficient detail to properly monitor and manage the work and as a minimum shall include the following:

a. the work shall be divided into activities by acceptance section and phase of work (e.g. preconstruction structure and property condition surveys, blasting, dredging)

b. separate activities shall reflect each mobilization and demobilization of each major plant

c. activities shall be identified by associated bid item

d. all required and proposed submissions shall be included in the progress schedule

e. Government and other agency activities that could impact progress shall be shown (e.g. Government surveys, navigation aid relocations, etc.)

The schedule shall extend from NTP to the established contract completion date.

The initial progress schedule shall be included with the solicitation proposal and demonstrate that the proposed plant and resources are capable

SECTION 01 32 01.00 10 Page 4 of performing the work as scheduled. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Periodic schedule updates shall be provided monthly with each payment request, and whenever there is a change in logic or time extension. Each submission shall include the data disks containing the project schedule adhering to the SDEF format specified in ER 1-1-11, Appendix A; the earnings report indicating monthly and cumulative earnings; a narrative report with a description of the activities identifying the critical path(s), current or anticipated problems of delays and their impact, and proposed corrective actions; and the schedule reports containing activity number, activity description, original duration, remaining duration, early start date, early finish date, late start date, late finish date and total float. The schedule reports shall be sorted as activity report, logic report listing preceding and succeeding activities for each activity, total float report listed in ascending order by early state date, early state sort and earning report.

A network diagram shall be submitted with the initial submission and each update. The network diagram shall depict the order, sequence and interdependence of activities, shall clearly indicate milestone dates and projected early and late earnings.

In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.2 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.2.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

- Dredging sequencing

- Dredging plant(s) type, size, and anticipated daily production rate(s)

- Environmental windows to include applicable mobilization and demobilization of equipment to include but not limited to pipeline

- Acceptance Sections (by Reach per contract drawings and/or contractor requested areas approved by the Government)

- Mobilization and demobilization durations

- Minimum of one activity per CLIN

- Placement Area Work (if applicable)

- Submitted schedule timeline calendar days for each month matches the calendar days per month for the respective year

3.2.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

Less than 2 percent of all non-procurement activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

SECTION 01 32 01.00 10 Page 5

3.2.3 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.2.4 Mandatory Tasks

Include the following activities/tasks, if applicable, in the initial project schedule and all updates f or each r espect i ve dr edge ar ea or r each.

a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each to include but not limited to QCP, APP, and EPP).

b. Environmental Windows (start to finish)

c. Acceptance Sections (as approved by Govt)

d. Placement Area Survey and Inspection - Pre-Dredge

e. Placement Area Survey and Inspection - Post-Dredge

f. Mobilization

g. Demobilization

3.2.5 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: environmental permit approvals by State regulators, inspections, surveys (before dredge (B/D) and after dredge (A/D)) and Notice to Proceed (NTP) for phasing requirements.

3.2.6 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 . This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site: http://rms.usace.army.mil .

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 AREA 4 Area of work (Government approved Acceptance Section)

SECTION 01 32 01.00 10 Page 6

Field Activity Code Length Description

3 MODF 6 Modification Number

4 BIDI 6 Bid Item (CLIN)

*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the

FEATURE OF WORK field requirements.

3.2.6.1 Workers Per Day (WRKP)

Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

3.2.6.2 Area of Work Coding (AREA)

Assign Work Area code to activities based upon the Govt approved Acceptance Section in which the activity occurs.

Not all activities are required to be Work Area coded. A lack of Work Area coding indicates the activity is not resource or space constrained.

3.2.6.3 Modification Number (MODF)

Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.2.6.4 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs. An activity can have only one BIDI (CLIN) Code.

3.2.7 Contract Milestones and Constraints

Milestone activities are to be used for significant project events

SECTION 01 32 01.00 10 Page 7 including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.

3.2.7.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged.

3.2.7.2 End Project Finish Milestone and Constraint

The last activity in the schedule must be a finish milestone titled "End Project."

Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

3.2.7.3 Interim Completion Dates and Constraints

Constrain contractually specified interim completion dates (to include applicable Environmental Windows) to show negative float when the calculated late finish date of the last activity in that phase is later than the specified interim completion date.

3.2.7.3.1 Start Phase

Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work.

3.2.7.3.2 End Phase

Use a finish milestone as the last activity for a project phase. Call the finish milestone "End Phase X" where "X" refers to the phase of work.

3.2.8 Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, Environmental Windows, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop Seasonal Calendar(s) and assign to seasonally affected activities as applicable.

If an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated adverse

SECTION 01 32 01.00 10 Page 8 weather delay work days provided in the Supplementary Special Contract Requirements. Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends .

3.2.9 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Acknowledged" may have no predecessor logic, and the last activity -"End Project" may have no successor logic.

Predecessor open ended logic may be allowed in a time impact analyses upon the Contracting Officer's approval.

3.2.10 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

3.2.11 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer.

Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.2.12 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.

3.2.13 Original Durations

Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.

3.2.14 Leads, Lags, and Start to Finish Relationships

Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

b. Start to Finish (SF) relationships are prohibited.

SECTION 01 32 01.00 10 Page 9

3.2.15 Retained Logic

Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(s) starts and the predecessor activity(s) has not finished (out-of-sequence progress). Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") are not be allowed.

3.2.16 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value or quantity of material dredged.

Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management.

3.2.17 Remaining Duration

Update the remaining duration for each activity based on the number of estimated work…