Section C Full Scope of Work.pdf

PDF 485 KB Posted

Attached to
Stop-Log Procurement Oologah Federal contract opportunity
Solicitation number
W912BV22Q0082
Issued by
Department of the Army Corps of Engineers Engineering District Tulsa

About this file

This document outlines a forthcoming federal solicitation for the procurement of stop-logs and a lifting beam. The U.S. Army Corps of Engineers Tulsa District will issue solicitation number W912BV22Q0082 to procure three stop-logs and at least one lifting beam as a small business set-aside supply contract under NAICS code 332312. The anticipated award date is October 11, 2022, with quotes due by September 23, 2022. The fabricator must be certified under the AISC Quality Certification Program and hold an Fracture Critical Endorsement. All welding must comply with AWS D1.5. The contractor will fabricate the stop-logs and lifting beam, perform testing, and deliver the items to the project site. The contractor must submit various documents and plans prior to starting work.

View the file

Other files for this federal contract opportunity

Other files attached to Stop-Log Procurement Oologah, newest first.
File Type Posted
W912BV22Q0082-0001.pdf PDF
OOL22SL_PLANS_RTA.pdf PDF
Attachment L-1.docx DOCX document
SOLICITATION W912BV22Q0082.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Solicitation # W912BV-22-Q-0082

Section C

Oologah Lake

Replace Stoplogs- Fabrication and Delivery Only Version Date:7.21.22

Date: June 10, 2022

SECTION 00 11 00

PRICING SCHEDULE

Revision Date: 5.18.2022

Submittal Review Date: 5.27.2022

Item No.

Description

Estimated Quantity

Unit

Unit Price

Amount

BASE

BID

Field Inspection

JOB

0002 Stoplog – OOL22SL001 1 EA $ $

0003 Stoplog – OOL22SL002 1 EA $ $

0004 Stoplog – OOL22SL003 1 EA $ $

0005 Lifting Beam – OOL22LB001 1 EA $ $

TOTAL BASE BID AMOUNT $

TOTAL PROPOSAL $

PROPOSAL SCHEDULE NOTES

1. Offerors must insert a price on all numbered items of the PRICING SCHEDULE. Failure to do so will disqualify the Offer.

2. All costs for items of work not listed separately in the PRICING SCHEDULE or specifically mentioned to be included in a particular item price shall be included in the listed item price most closely associated with the work involved.

3. All quantities are estimated except where the unit is JOB.

4. Only one contract will be awarded under this solicitation.

-- End of Document –-

00 11 00 Page 1

Oologah Replace Stoplogs C22-SL-OOLOGAH 07/28/22 Procurement Documents

SECTION 01 11 00.00 47

SUMMARY OF WORK

08/ 15, CHG 1: 05/ 21, SWT 1/ 19/ 22

PART 1 GENERAL

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2014) Safety and Health Requirements Manual

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

This section provides a general summary of the work to be performed to fabricate, paint and deliver stoplogs and lifting beam, as well as perform all testing as required. See the specifications and drawings for detailed requirements. The Contractor must provide all plant, materials, equipment, labor, instruments, tools, subcontractors, supervision, management, and travel necessary to complete all work in accordance with the summary of work, attached drawings, specifications, and all other contract documents and requirements. No materials, equipment, utilities, or labor will be provided by the Government.

1.2.2 Scope of Work

The following is a summary of the major items of work included in this Contract. All the items listed here are described in greater detail throughout the rest of the technical sections. The work includes, but is not limited to:

a. Fabricate the stoplogs as indicated. Add unique identifier and final weight to each unit.

b. Fabricate, proof load test, and add markings per ASME B30.20 the lifting beam.

c. Hang test the stoplogs for center of gravity determination and lifting lug placement.

d. Stack test the stoplogs.

e. Blasting and painting of stoplogs and lifting beam.

f. Delivery and offloading of stoplogs and lifting beam to the Oologah Area Office Storage Compound. Each stoplog must be shipped immediately after successful completion of Government Witness Point Inspections, painting, and testing. All the stoplogs and the lifting beam will become property of the government.

SECTION 01 11 00.00 47 Page 1

1.2.3 Location

Fabrication and painting must be done in shop. The stoplogs and lifting beam will be delivered and offloaded the at the Oologah Area Office Storage Compound as indicated on the contract drawings.

1.3 EXPLANATION OF CONTRACT AUTHORITY AND RELATIONSHIPS

The U. S. Army Corps of Engineers (USACE), Tulsa District will award and administer this contract and will be the sole authority to interact contractually with, direct, and provide oversight to the Contractor.

References to any other organization, entity, or individual either directing, authorizing, approving, or in any other way contractually interacting with the Contractor must denote such action by the designated representative(s) of the Contracting Officer, USACE, Tulsa District.

1.4 SAFETY

All work at USACE project locations must be performed in accordance with the latest edition of EM 385-1-1 and all subsequently issued interim changes and errata, CFR 1910, 29 CFR 1926 and other references as listed herein. Matters of interpretation of the safety standards must be submitted to the COR for resolution before starting work. Where the regulations conflict, the most stringent requirements must apply.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

3.1 DELIVERY AND STORAGE

Submit a delivery/shipping plan in accordance with Section 05 59 20

FABRICATION OF HYDRAULIC STEEL STRUCTURES.

-- End of Section --

SECTION 01 11 00.00 47 Page 2

SECTION 01 20 00.00 47

PRICE AND PAYMENT PROCEDURES

11/ 20, CHG 1: 02/ 21, SWT 4/ 7/ 22

PART 1 GENERAL

1.1 SINGLE JOB PAYMENT ITEMS

Payment items for the work of this Contract for which Contract job payments will be made are listed in the SCHEDULE and described below. All costs for items of work, which are not specifically mentioned to be included in a particular job or unit price payment item, are included in the listed job item most closely associated with the work involved. The job price and payment made for each item listed constitutes full compensation for furnishing all plant, labor, materials, and equipment, and performing any associated Contractor quality control, environmental protection, meeting safety requirements, tests and reports, and for performing all work required for which separate payment is not otherwise provided.

1.1.1 CLIN 0001 Field Inspection

1.1.1.1 Payment

Payment for work pertaining to the prefabrication and any subsequent field inspections and measurements required in this contract will be made under CLIN 0001. Price must be full compensation for furnishing all plant, materials, equipment, labor, instruments, tools, subcontractors, supervision, and management required for the field inspection and measurements, processing of materials, and all related miscellaneous operations in the final locations as shown and specified.

1.1.1.2 Unit of Measure

Unit of measure: JOB

1.2 UNIT PRICE PAYMENT ITEMS

Payment items for the work of this Contract on which the Contract unit price payments will be made are listed in the PRICING SCHEDULE and described below. The unit price and payment made for each item listed constitutes full compensation for furnishing all plant, labor, materials, and equipment, and performing any associated Contractor quality control, environmental protection, meeting safety requirements, tests and reports, and for performing all work required for each of the unit price items.

1.2.1 CLIN 0002- 0004 Stoplog

1.2.1.1 Payment

Payment for work pertaining to each stoplog unit will be made under CLINs 0002 - 0004. Price must be full compensation for furnishing all plant, materials, equipment, labor, instruments, tools, subcontractors, supervision, testing, and management required for the stoplog units, processing of materials, and all related miscellaneous operations. Payment will be made after testing, delivery, and offloading of each stoplog unit..

SECTION 01 20 00.00 47 Page 1

1.2.1.2 Unit of Measure

Unit of measure: EACH.

1.2.2 CLIN 0005 Lifting Beam

1.2.2.1 Payment

Payment for work pertaining to the lifting beam will be made under CLINs 0005. Price must be full compensation for furnishing all plant, materials, equipment, labor, instruments, tools, subcontractors, supervision, testing, and management required for the lifting beam, processing of materials, and all related miscellaneous operations. Payment will be made after testing, delivery, and offloading of the lifting beam.

1.2.2.2 Unit of Measure

Unit of measure: EACH. PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 20 00.00 47 Page 2

SECTION 01 32 16. 50 47

SMALL PROJECT PROGRESS SCHEDULES

CIVIL WORKS

08/ 18, CHG 1: 08/ 20, SWT 4/ 19/ 22

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification.

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (2017) Administration -- Project Schedule

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. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

Submittals SD-01 and SD-07 shall be submitted as separate 4025's for approval.

SD-01 Pre fabrication Submittals

Project Schedule ; G

Recovery Schedule ; G

Completion Schedule ; G

SD-07 Certificates

Project Scheduler Qualifications ; G

a. Detailed documentation of experience in scheduling (school, training, software, years scheduling, etc.)

b. Minimum of 3 previously developed, created, and maintained projects similar in nature and complexity to the project, detailing name, contract amount, and location of projects.

c. Minimum of 2 years experiences scheduling fabrication projects similar in nature of this project.

d. Qualifications meet or exceed requirements under paragraph 1.3

"PROJECT SCHEDULER QUALIFICATIONS - DESIGNATED AUTHORIZED

REPRESENTATIVE (DAR)

SECTION 01 32 16.50 47 Page 1

1.3 PROJECT SCHEDULER QUALIFICATIONS DESIGNATED AUTHORIZED REPRESENTATIVE

(DAR)

Designate an authorized Project Schedule representative(DAR)to be responsible for the preparation of the schedule and all required updating and production of reports. The DAR shall have no other responsibilities involving the project unless approved by the Contracting Officer. The DAR must have a minimum of 2-years' experience scheduling fabrication projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. DAR must have a comprehensive knowledge of CPM scheduling principles and application. DAR shall be same person or employee of a company approved under paragraph 1.2 "Submittals", SD-07 Certificates. A DAR change shall be submitted and approved,per paragraph 1.2 "Submittals", before new DAR takes over responsibilities from previous DAR. DAR to be responsible for the preparation of the schedule, all required updating, preparing of reports, and all requirements of this specification. DAR shall have experience in the use of the scheduling software that meets the requirements of this specification. USACE reserves the right to have DAR removed/replaced when schedule management, expertise, and performance are determined to be not meeting the requirement set forth in this specification. If so requested by USACE, DAR shall come to site or USACE office for any meeting.

PART 2 PRODUCTS

2.1 Software

a. Primavera

b. Microsoft Project

c. Microsoft Excel

If Microsoft Project or Microsoft Excel is used, manual inputting of activities into RMS shall be required.This includes all codes, cost loading, and other items listed (that can be manually inputted). If using Primavera, then a SDEF shall be created and inputted into RMS only when USACE approves SDEF, not SDEF shall be loaded into RMS without USACE approval.SDEF shall be created from within the scheduleing software. Using a third party software for creating SDEF is prohibited.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare Project Schedule for approval as a Bar Chart Schedule, or Project Schedule, as specified herein. Provide submittal (transmitted thru RMS via 4025) for a cost-loaded network diagram (Gantt/bar chart) for approval no later than 30 calendar days after award date. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. Schedule layout shall be in sequential order from award to End Project. The scheduling of the entire project, including the design and fabrication sequences, is required. The scheduling of fabrication , design and fabrication is the responsibility of the Contractor. Contractor management personnel shall actively participate in its development.

Subcontractors and suppliers, Designers, Subcontractors and suppliers working on the project shall also contribute in developing and maintaining

SECTION 01 32 16.50 47 Page 2 an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project-monitoring tool. Dates based on calendar days, not working days.Software used shall provide equal settings in all schedule submissions to the Government.

Contracting Officer will have the right to have Contractor provide additional detail to schedule as deemed warranted besides following list.

a. If mobilization activity is used, a demobilization activity shall be in the schedule. The combined total between mobilization and mobilization shall be split between mobilization (60%) and demobilization (40%).

b. Once Original Durations are approved, they cannot be changed.

c. Original durations shall not be over 20 calendar days. Only exceptions are Summary, Hammock, and Level of Effort activities.

d. Award shall be a start milestone, first activity in schedule with no activity ahead of it, have no predecessors.The first activity of the schedule shall be called " award ".

e. End Project activity shall be based on contract completion date. Use "project must end by" or equivalent in software. Do not use any other constraints.Do not place activity constraint on End Project. End Project activity shall be the only activity without a successor.

f. Project Activity Codes must be Project Level, not Global or EPS level.

g. Project Calendars must be Project Level, not Global or Resource level.

h. Project Schedule Default for defining Activity Duration Types must be set to "Fixed Duration & Units", except for Milestones.

i. Project Schedule Default for defining Percent Complete Types must be set to "Physical"

j. Project Schedule Options for defining Critical Activities must be set to "Longest Path"

k. Project Schedule Option for defining Scheduling Progressed Activities must be set to "Retained Logic".

l. Project Schedule Option for defining Expected Finish, the check box will not be checked.

m. Project Schedule Option for Compute Total Float as must be set to "Smallest of Start Float and Finish Float"

n. Project Admin Preference for Hours per Time Period must remain the default "8.0 hr/day, 40 hr/week, 172 hr/month, 2000 hr/year". Set Calendar Work Hours/Day to 8.0 Hour days. Using any other hr/day besides 8 hours is prohibited.

o. Project cost loading using a single lump sum resource. The Price/Unit must be $1/hr, Default Units/Time must be "8h/d", and settings "Auto Compute Actuals" and "Calculate costs from units" selected (CHECK BOX). Contractor shall create project resource that does not match any resource ID and resource name in the USACE P6

SECTION 01 32 16.50 47 Page 3 database that has been dedicated to other Contractors.

p. Project Activity ID's must not exceed 10 character. Alpha, spaces, or numbers are allowed. All other characters are prohibited.

q. Project Activity Names/Descriptions shall be no more than 30 characters, including spaces. Activity Names/Description shall not be duplicated, each shall be unique. Abbreviations shall be used to get within the 30 character limit.

r. Calendars shall be 5 day or 7 day. No 1, 2, 3, 4, or 6 day calendars or hour calendars are allowed unless approved by Government and have 8 hour work days assigned to them.

s. Provide a milestone for "RED ZONE MEETING"

t. Using a SS, FF, or FS relationship in unison as a predecessor or successor to an activity is prohibited.

u. Lags shall not be more than 5 working days or 7 calendar days.

v. Start to Finish (SF) relationships, along with Leads (negative lags) are prohibited.

w. No constrained dates are allowed in the schedule other than those specified herein.

x. Using "Expected Finish", "Suspend", or "Resume" as part of the activity Status is prohibited.

y. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

z. Using BOD, Beneficial Occupancy, Substantial Completion, Turn Over, or any other description related to Owner acceptance as an activity and/or descriptions is prohibited.

aa. Using "Expected Finish", "Suspend", or "Resume" as part of the activity Status is prohibited.

ab. The Contractor shall not schedule meetings, Government reviews, or responses during the last two weeks of December or other official federal Government holidays (including Friday after Thanksgiving) and shall exclude such dates and periods from any durations specified for Government actions.

3.1.1 Project Schedule Submittal Activity Breakdown

Contractor shall provide a submittal activity for administrative, design, fabrication , or close-out activity that requires a submittal(even if submittal is for information only) broken down into the following four (4)Descriptions: "Prep", "Submit", "Government Review", and "Approval", unless activity is for procurement, then add "Procure","Fabricate","Deliver", "Payment". For activity that involves a procurement, then "Payment" will be the only activity cost loaded. The activity called "Prep" shall represents time to prepare submittal or design before submitting. The original duration for Submit shall not include any days for Prep. Original duration for "Submit" and "Approval" activity shall be one (1) calendar day. Government Review shall be based

SECTION 01 32 16.50 47 Page 4 on contract requirements. If contract requirements does not give original duration for Government review in work or calendar days, then duration shall be 30 calendar days.

3.1.2 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 . Contractor shall create the schedule using the following codes for each individual project. Contractor shall define each activity code as a PROJECT activity code. All Activity Codes shall be developed and assigned to activities as detailed herein.

The following activity codes, designated under column 1 by "YES", are for this project. Remaining activity codes shall be added as needed at a later date.

Assign Code to activity

Field Activity Code

Length Description

1 WRKP 3 Workers Per Day

YES 2 RESP 4 Responsible Party

3 AREA 4 Area of Work

4 MODF 6 Modification Number

YES 5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of Work

7 CATW 1 Category of Work

YES 8 FOW 20 Feature of Work

*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. Activity Code shown shall be exactly used in the software.

3.1.3 Responsible Party Coding (RESP)

Assign responsibility code (RESP) for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.

a. Activities coded with a Government "GOVT" Responsible Party code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and( award ) for phasing requirements. Government "GOVT" Responsible Party code shall not be used for any activity that has costs associated with

it. For activities that require Government approval and must have cost associated with them, the Contractor shall use "ABTG" for those activities.

b. Activities cannot have more than one Responsible Party code. Examples

SECTION 01 32 16.50 47 Page 5 of acceptable Responsible Party code values for (RESP) are: DOR (for the designer of record); ELEC (for the electrical subcontractor);

MECH(for the mechanical subcontractor); and GOVT (for USACE). Assign Responsible Party code for all activities. Unacceptable code values are abbreviations of the names of prime contractors or subcontractors.

RESP codes shall be alpha; numeric is not allowed for RESP codes.

Responsible Party codes shall be imported through the SDEF conversion of the schedule into RMS. Manual inputting of Responsible Party codes into RMS is prohibited unless using Microsoft Project or Microsoft Excel.

3.1.4 Bid Item Coding (BIDI)

Assign a Bid Item code (BIDI) to all activities using the Contract Line Item Number (CLIN) Schedule to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI code. Bid Item codes (BIDI) shall be imported through the SDEF conversion of the schedule into RMS. Manual inputting of Bid Item (BIDI) codes into RMS is prohibited unless using Microsoft Project or Microsoft Excel.

3.1.5 Feature of Work Coding (FOW)

Assign a Feature of Work code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan Features of Work. Feature of Work codes shall be created as part of the QC Plan and inserted into the schedule. Definable Features of Work are defined in Section 01 45 00.10 15 QUALITY CONTROL SYSTEM and are required as a minimum. The Contractor's has the option to create and provide additional Features of Work codes. These additional codes shall be included in the QC Plan for approval. For new Feature of Work codes required after an executed modification, the Contractor shall revise Feature of Work codes as part of QC Plan and resubmit for approval before inserting into the schedule's Feature of Work code listing. An activity can have only one Feature of Work code. Every activity shall have a Feature of Work code. Feature of Work codes (FOW) shall be imported through the SDEF conversion of the schedule into RMS. Manual inputting of Features of Work codes into RMS is prohibited unless using Microsoft Project or Microsoft Excel.

3.1.6 FAILURE TO ACHIEVE PROGRESS

Should the progress fall behind the approved project schedule for reasons other than those that are excusable within the terms of the contract, the Contracting Officer may require a written recovery plan for approval and or a recovery schedule based on section 01 32 01.00-3.4.3 Recovery or fabrication Completion Project Schedule Submission. In either case, the plan must detail how progress will be made-up to include which activities will be accelerated by adding additional crews, longer work hours, extra work days, etc.

3.1.7 Artificially Improving Progress

Artificially improving progress by means such as, but not limited to, revising the schedule logic, modifying or adding constraints, shortening activity durations, or changing calendars in the project schedule is prohibited. Indicate assumptions made and the basis for any logic, constraint, duration and calendar changes used in the creation of the recovery plan. Any additional resources, manpower, or daily and weekly work hour changes proposed in the Recovery or fabrication Completion plan

SECTION 01 32 16.50 47 Page 6 must be evident at the work site and documented in the daily report along with the Schedule Narrative Report.

3.1.8 Failure to Perform

Failure to perform work and maintain progress in accordance with the supplemental Recovery or fabrication Completion plan may result in an interim and final unsatisfactory performance rating and may result in corrective action directed by the Contracting Officer pursuant to 52.242-14 Suspension of Work , 52.212--4(m) Termination for Cause , and other contract provisions.

3.1.9 Recovery Schedule or fabrication Completion Project Schedule Submission

If the Contractor falls behind his approved schedule (behind the LS/LF cash flow curve of more than 20 calendar days of negative total float), or performs the work in such a manner that the network diagram and mathematical analysis no longer indicate reasonable logic and duration for completion of the work by the current contract completion date, as determined by the Contracting Officer, the Contractor shall promptly provide a supplemental Recovery Schedule to regain the original schedule and show project will complete the work by the current contract completion date, or a supplemental fabrication Completion ( FC) schedule to show when project will be completed passed the current contract required completion date, as approved by the Contracting Officer.Recovery or FC schedule shall be transmitted via 4025 within the time frame the Contracting Officer has given, with all documentation and requirements per specifications. The Recovery or FC schedule shall be resource loaded, utilizing paragraphs

3.1.2 "Standard Activity Coding Dictionary", 3.1.3 "Responsible Party Coding (RESP)", and add WRKP activity code to each activity with crew size and productivity for each remaining activity, and indicating overtime, weekend work, and/or double shifts needed to either regain the the schedule (Recovery) or show when project will be completed ( FC) , in accordance with 52.242-2 Production Progress Reports , without additional cost to the Government. The Recovery or FC schedule once submitted,accepted and approved may replace the original approved schedule as the official contract schedule. If required by Contracting Officer, the original approved schedule shall be updated monthly, in addition to the Recovery or FC schedule, and monitored by the Contractor and Contracting Officer to determine the effect of the Recovery or FCS progress for comparison to determine has the Recovery Schedule progressed to regain the rate of progress for timely completion to meet contract required completion date or if the FC will met the fabrication completion date.

The Contractor shall not artificially improve his progress by revising the schedule logic restraints, using calendars other then 5 or 7 day, or shortening future work activity durations. The Contractor may improve his progress by performing sequential work activities concurrently or by performing activities more quickly than planned, but such improvements shall be indicated on the Recovery or FC Schedule and shall not be recorded on the official schedule until they have actually been achieved by the Contractor. The additional resources required to improve the progress must be evident on the work site.

Failure of the Contractor to perform work and maintain progress in accordance with the supplemental Recovery or FC schedule may result in an interim and final unsatisfactory performance rating and/or may result in

SECTION 01 32 16.50 47 Page 7 corrective action by the Contracting Officer in accordance with 52.242-2 Production Progress reports .

After Recovery or FC submittal is accepted and approved and before any manual entry or SDEF is loaded into RMS, the Contractor shall update the Recovery or FC Schedule with actual data and present the back up schedule file and SDEF file (if using Primavera P6) within three (3) working days to USACE for review. Once that schedule is reviewed and approved and notification from USACE is given, Contractor will then manually insert or load SDEF into RMS.Recovery or FC Schedule shall meet all requirements of this specification.

3.1.10 WEEKLY PROGRESS MEETINGS

Conduct a weekly progress meeting with the Government for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks. Provide a weekly update report, with current actual start and actual finish dates, remaining durations, and percent completes on activities that has have been status between weekly progress meetings utilizing layouts part of the scheduling software. Use the current approved schedule update for the purposes of this meeting and for the production and review of reports. At the weekly progress meeting, address the status of RFIs, RFPs and Submittals.The Contractor shall provide a copy of the agenda for weekly progress meeting at least 24 hours before the meeting begins.The Contractor shall provide post-meeting minutes within forty-eight (48) hours of the conclusion of the meeting.

3.1.11 OWNERSHIP OF FLOAT

Except for the provision given in the paragraph entitled "Impact to Early Completion Schedule ", float available in the schedule, at any time, shall not be considered for the exclusive use of either the Government or the Contractor including activity and/or project float. Activity float is the number of work days that an activity can be delayed without causing a delay to the "End Project" finish milestone. Project float (if applicable) is the number of work days between the projected early finish and the contract completion date milestone.

3.2 Approved Project Schedule (Bar Chart)

Use the approved Project Bar Chart Schedule to measure the progress of the work and to aid in evaluating time extensions. The Bar Chart will provide the basis for all progress payments. If the Contractor fails to submit any Bar Chart Schedules within the time prescribed, the Contracting Officer may withhold approval of progress payments until the Contractor submits the required Bar Chart Schedule.Contractor shall provide a schedule update every thirty (30) calendar days from the last approved and accepted update even if no pay application is presented. This update shall be transmitted thru RMS via 4025. If using P6, SDEF shall not be loaded until USACE give approval to do so.

3.3 Default Terms

Failure of the Contractor to comply with the requirements of the Contracting Officer shall be grounds for a determination, by the Contracting Officer, that the Contractor is not prosecuting the work with sufficient diligence to ensure completion within the time specified in the contract. Upon making this determination, the Contracting Officer may

SECTION 01 32 16.50 47 Page 8 terminate the Contractor's right to proceed with the work, or any separable part of it, in accordance with the default terms of the contract.

3.4 BASIS FOR PAYMENT AND COST LOADING

As part of the submittal and modification process, USACE shall review cost loading and to evaluate the cost loading to determine if cost loading is reasonable and without front end loading. Non-compliance with this requirement will result in an automatic rejection of Project Schedule submittal or approval of executed modification activities that costs associated with them. Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer. See additional cost loading requirements under paragraphs 3.4.1 "As-Built Drawings, O&M Manuals", and 3.4.2 "Correction of Punch List". Each activity shall be cost loaded and subtotaled by CLINs whether or not there is a cost associated with the activity.

3.4.1 As-Built Drawings, O&M Manuals

If there is no separate contract line item (CLIN) for As-Built drawings and/or O&M Manuals, cost load the "Approval of As-Built drawings" and "Approval of O&M manuals" activity with 1 percent of the present contract value. Activity will be declared 100 percent complete upon the Government's approval of all As-Built drawings and O&M manuals.

3.4.2 Corrections of Punch List

Cost load the "Correction of punch list/ Gov't final inspection" activity(ies) total not less than 1 percent of the present contract value.

Activity(ies) may be declared 100 percent complete upon the Government's verification of completion and corrections of all punch list work identified during Government pre-final inspection(s).

3.5 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the Periodic Monthly Schedule Update, Recovery Schedule Monthly Update, or fabrication Completion Monthly Update schedule and will result in rejection of payment requests until compliance is met.

Until the Periodic Monthly Schedule Update, Recovery Schedule Monthly Update, or fabrication Completion Monthly Update or executed modification fragnet to be added to schedule are approved, no Pay Applications shall be processed or approved for payment. If Pay Application is presented before acceptance and approval of any schedule submittal, the Pay Application will be returned with no action taken. 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 or reject Pay Application with no further action until such corrections are made.

In the case where the Periodic Monthly Schedule Update, Recovery Schedule Monthly Update, or fabrication Completion Monthly Update schedule is status and shows the project is 10 calendar days or more in negative total float, the Contracting officer may withhold 10 percent in retainage.

SECTION 01 32 16.50 47 Page 9

3.6 SUBMISSION REQUIREMENTS

With each month's Pay Estimate/Invoice, Contractor shall provide a CPRW (Contractors Pay Request Worksheet, generated in RMS) to USACE for approval. Once approved, Contractor shall transmit in RMS for approval the Prompt Payment form and schedule updated backup files.

Submit the following items for the Project,Recovery,or fabrication Completion submittals, and every Periodic Schedule Update throughout the life of the project.

a. Narrative Report(per 3.6.1)

b. Back up file of schedule

c. SDEF file (if P6 utilized)

d. Earnings Report by CLIN (per 3.6.2)

e. PDF file of schedule (per 3.6.3 and sub paragraphs)

f. PDF Longest/Critical Paths (per 3.6.4)

3.6.1 Narrative Report

The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for any problems, either current or potential, which are revealed through that analysis. The narrative report shall not be used to provide comments or clarifications to a schedule submittal. Include the following information as minimum in the Narrative Report:

a. Shall be addressed to the COR for the project.

b. Statement declaring who is the Designated Authorized Representative (DAR) for Schedule.

c. Compliance with paragraphs 1.1 "References"

d. Specifically reference, on an activity by activity basis, all changes made since the previous period and relate each change to documented, approved schedule changes.

e. Identify and discuss the work scheduled to start in the next update period.

f. A description of activities along the two most critical paths where the total float is less than or equal to 20 work days.

g. A description of current and anticipated problem areas or delaying factors and their impact and an explanation of corrective actions taken or required to be taken.

h. Identify and explain why activities based on their calculated late dates should have either started or finished during the update period but did not.

i. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was

SECTION 01 32 16.50 47 Page 10 needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, lag changes, resource changes, and actual start and finish date changes.

j. Identify and discuss out-of-sequence work.

3.6.2 Earnings Report by CLIN

A compilation of the Total Earnings on the project from the award date to the data date. Group activities by CLIN number and sort by activity number. This report must also provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following columns for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

3.6.3 Bar (Gantt) Chart

A Bar (Gantt) Chart is required for depicting and displaying the order and interdependence of activities and the sequence in which the work is to be accomplished. The Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.6.3.1 Continuous Flow

Show a continuous flow from left to right with no arrows from right to left.

3.6.3.2 Project Milestone Dates

Show dates on the diagram for start of project, any contract required interim completion dates, and contract completion dates.

3.6.3.3 Longest/Critical Path

Show all activities on the longest/critical path. Clearly show the longest/critical path, using RED. The critical path is defined as the longest path.

3.6.3.4 Banding

Organize activities using the WBS or as otherwise directed to assist in the understanding of the activity sequence. Typically, this flow will group activities by major elements of work, category of work, work area and/or responsibility.

3.6.4 Longest/Critical Path Bar (Gantt) Chart

The Longest/Critical Path Bar Chart main float paths shall be depicted and displayed with the order and interdependence of activities and the sequence in which the work is to be accomplished. Show all activities on the longest path. Clearly show the longest path, using RED. Each float path shall be separately and in stair step fashion. Do not use WBS format.

3.7 REQUESTS FOR TIME EXTENSIONS

Provide a justification of delay to the Contracting Officer in accordance with the contract provisions and clauses for approval within ten (10)

SECTION 01 32 16.50 47 Page 11 calendar days of a delay occurring. Also prepare a time impact analysis for each Government request for proposal (RFP) to justify time extensions.

3.7.1 Justification of Delay

Provide a description of the event(s) that caused the delay and/or impact to the work. As part of the description, identify all schedule activities impacted. Show that the event that caused the delay/impact was the responsibility of the Government. Provide a time impact analysis that demonstrates the effects of the delay or impact on the project completion date or interim completion date(s). Multiple impacts must be evaluated chronologically; each with its own justification of delay. With multiple impacts consider any concurrency of delay. A time extension and the schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.

3.7.2 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by the Contracting Officer based on industry standard AACE 52R-06 . Utilize a copy of the last approved schedule prior to the first day of the impact or delay for the time impact analysis. If Contracting Officer determines the time frame between the last approved schedule and the first day of impact is too great, prepare an interim updated schedule to perform the time impact analysis. unless approved by the Contracting Officer, no other changes may be incorporated into the schedule being used to justify the time impact.

3.7.3 Forensic Schedule Analysis (Retrospective Analysis)

Prepare an analysis for approval by the Contracting Officer based on industry standard AACE 29R-03 .

3.7.4 Fragmentary Network (Fragnet)

Prepare a proposed fragnet for time impact analysis. The proposed fragnet must consist of a sequence of new activities that are proposed to be added to the project schedule to demonstrate the influence of the delay or impact to the project's contractual dates. Clearly show how the proposed fragnet is to be tied into the project schedule including all predecessors and successors to the fragnet activities. Typically, report shall contain Activity ID, Activity Description, Current Schedule, Data Date, Start Date, Finish Date, Duration in Calendar Days, Predecessor(s), Successor(s), Relationship Type, Constraint, and Calendar. The proposed fragnet must be approved by the Contracting Officer prior to incorporation into the project schedule.

3.7.5 Submission Requirements for Time Extensions

Submit a justification for each request for a change in the contract completion date based upon the most recent approved updated project schedule at the time of the impact. Such a request shall be in accordance with the requirements of other appropriate Contract Clauses and shall include, as a minimum:

a. List of affected activities, with their associated project schedule activity number (3.7.4 Fragmentary Network (Fragnet).

b. Brief explanation of the causes of the change (narrative).

SECTION 01 32 16.50 47 Page 12

c. An analysis of the overall impact of the changes proposed (part of narrative).

d. A sub-network of the affected area.(detailed fragnet breakdown per 3.7.4)

e. .pdf and backup file schedule at time of impact (using data date of start of impact)

f. .pdf and Backup file of schedule after inserting impact activities (using same data date of start of impact)

3.7.6 Time Extension

The Contracting Officer must approve the Justification of Delay including the time impact analysis before a time extension will be granted. No time extension will be granted unless the delay consumes all available Project Float and extends the projected finish date ("End Project" milestone) beyond the Contract Completion Date. The time extension will be in calendar days.

Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay will not be a cause for an extension to the performance period, completion date, or any interim milestone date.

3.7.7 Impact to Early Completion Schedule

No extended overhead will be paid for delay prior to the original Contract Required Completion date for an Early Completion IPS unless the Contractor actually performed work in accordance with that Early Completion Schedule.

The Contractor must show that an early completion was achievable had it not been for the impact.

SECTION 01 32 16.50 47 Page 13

SECTION 01 33 00.00 47

SUBMITTAL PROCEDURES

08/ 18, CHG 4: 02/ 21, SWT 1. 20. 22

PART 1 GENERAL

1.1 SUMMARY

1.1.1 Submittal Information

The Contracting Officer may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections. Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

Units of weights and measures used on all submittals are to be the same as those used in the contract drawings.

1.1.2 Project Type

The Contractor's Quality Control (CQC) System Manager are to check and approve all items before submittal and stamp, sign, and date indicating action taken. Proposed deviations from the contract requirements are to be clearly identified. Include within submittals items such as:

Contractor's, manufacturer's, or fabricator's drawings; descriptive literature including (but not limited to) catalog cuts, diagrams, operating charts or curves; test reports; test cylinders; samples; O&M manuals (including parts list); certifications; warranties; and other such required submittals.

1.1.3 Submission of Submittals

Schedule and provide submittals requiring Government approval before acquiring the material or equipment covered thereby. Pick up and dispose of samples not incorporated into the work in accordance with manufacturer's Safety Data Sheets (SDS) and in compliance with existing laws and regulations.

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

Submittal requirements are specified in the technical sections. Examples and descriptions of submittals identified by the Submittal Description (SD) numbers and titles follow:

SD-01 Prefabrication Submittals

Submittals that are required prior to or at the start of fabrication .

For Government approved division 01 prefabrication submittals that are required prior to or commencing with the start of work must be submitted within 45 calendar days of contract award unless specified elsewhere in the specifications. For contractor approved division 01 submittals that are required prior to or commencing with the start of work must be submitted within 45 calendar days of contract award unless specified

SECTION 01 33 00.00 47 Page 1 elsewhere in the specifications.

Prefabrication Submittals include schedules and a tabular list of locations, features, and other pertinent information regarding products, materials, equipment, or components to be used in the work.

Certificates Of Insurance

List Of Proposed Subcontractors

List Of Proposed Products

Submittal Register

Work Plan

Quality Control (QC) plan

SD-02 Shop Drawings

Drawings, diagrams and schedules specifically prepared to illustrate the work. The contractor must provide shop drawings. Shop drawings must be approved by the government prior to start of fabrication.

SD-03 Product Data

Catalog cuts, illustrations, schedules, diagrams, performance charts, instructions and brochures illustrating size, physical appearance and other characteristics of materials, systems or equipment for some portion of the work.

SD-06 Test Reports

Report signed by authorized official of testing laboratory that a material, product or system identical to the material, product or system to be provided has been tested in accord with specified requirements. Unless specified in another section, testing must have been within three years of date of contract award for the project.

Report that includes findings of a test required to be performed on an actual portion of the work or prototype prepared for the project before shipment to job site.

Report that includes finding of a test made at the job site or on sample taken from the job site, on portion of work during or after installation.

Investigation reports

Daily logs and checklists

Final acceptance test and operational test procedure

SD-07 Certificates

Statements printed on the manufacturer's letterhead and signed by responsible officials of manufacturer of product, system or material attesting that the product, system, or material meets specification requirements. Documents m ust be dated after award of project contract

SECTION 01 33 00.00 47 Page 2 and clearly name the project.

Document required of Contractor, or of a manufacturer, supplier, installer or Subcontractor through Contractor. The document purpose is to further promote the orderly progression of a portion of the work by documenting procedures, acceptability of methods, or personnel qualifications.

SD-11 Closeout Submittals

Documentation to record compliance with technical or administrative requirements or to establish an administrative mechanism.

Submittals required for Guiding Principle Validation (GPV) or Third Party Certification (TPC).

Special requirements necessary to properly close out a fabrication contract. For example, shop drawings and final approved shop drawings .

1.2.2 Approving Authority

Office or designated person authorized to approve the submittal.

1.2.3 Work

As used in this section, fabrication and associated efforts required by contract documents, including labor necessary to produce submittal s, materials, products, equipment, and systems incorporated or to be incorporated in such fabrication . In exception, excludes work to produce SD-01 submittals.

1.3 SUBMITTALS

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

Submittals not having a "G" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Prefabrication Submittals

Submittal Register ; G

1.4 SUBMITTAL CLASSIFICATION

1.4.1 Government Approved (G)

Government approval is required for extensions of design, critical materials, variations, equipment whose compatibility with the entire system must be checked, and other items as designated by the Government.

Government approval is required for any variations from the Solicitation or the Accepted Proposal and for other items as designated by the Government.

Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, submittals are considered to be "shop drawings."

SECTION 01 33 00.00 47 Page 3

1.4.2 For Information Only

Submittals not requiring Government approval will be for information only. Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, they are not considered to be "shop drawings."

1.5 PREPARATION

1.5.1 Transmittal Form

Use the ENG Form 4025-R transmittal form for submitting both Government-approved and information-only submittals. Submit in accordance with the instructions on the reverse side of the form. These forms are included in the RMS CM software that the Contractor is required to use for this contract. Properly complete this form by filling out all the heading blank spaces and identifying each item submitted. Exercise special care to ensure proper listing of the specification paragraph and sheet number of the contract drawings pertinent to the data submitted for each item.

1.5.2 Submittal Format

1.5.2.1 Format of SD-01 Pre fabrication Submittals

When the submittal includes a document that is to be used in the project, or is to become part of the project record, other than as a submittal, do not apply the Contractor's approval stamp to the document itself, but to a separate sheet accompanying the document.

Provide data in the unit of measure used in the contract documents.

1.5.2.2 Format for SD-02 Shop Drawings

Provide shop drawings not less than 8 1/2 by 11 inches nor more than 30 by 42 inches , except for full-size patterns or templates. Prepare drawings to accurate size, with scale indicated, unless another form is required.

Ensure drawings are suitable for reproduction and of a quality to produce clear, distinct lines and letters, with dark lines on a white background.

a. Include the nameplate data, size, and capacity on drawings. Also include applicable federal, military, industry, and technical society publication references.

b. Dimension drawings, except diagrams and schematic drawings. Prepare drawings demonstrating interface with other trades to scale. Use the same unit of measure for shop drawings as indicated on the contract drawings. Identify materials and products for work shown.

Submit an electronic copy of drawings in PDF format.

1.5.2.2.1 Drawing Identification

Include on each drawing the drawing title, number, date, and revision numbers and dates, in addition to information required in paragraph

IDENTIFYING SUBMITTALS.

Number drawings in a logical sequence.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .