W912P522B0002_TSpecs_RTA_KYL Gearbox Heaters 2022-01-12.pdf
PDF 710 KB Posted
- Attached to
- Kentucky Lock Gearbox Heater System Federal contract opportunity
- Solicitation number
- W912P522B0002
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| W912P522B0003 Amend0001 KL Gearbox Heater 02.15.2022.pdf | ||
| W912P522B0002 Amend. 0001 TPlans 2022.02 (1).pdf | ||
| W912P522B0002 Amend. 0001 TPlans 2022.02 (2).pdf | ||
| W912P522B0002 TPlans_RTA-Certified Final_KYL Gearbox Heater System 2022-01-12.pdf | ||
| W912P522B0002 Bid Schedule - KY Lock Gearbox 01.06.2022.pdf | ||
| Solicitation W912P522B0002 KL Gearbox Heater 01.19.2022.pdf | ||
| Davis Bacon Act WD KY20220061.pdf | ||
| Site_Visit_Registration_Form_KLGearbox Heater.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 No. W912P522B0002
US Army Corps Of Engineers Nashville District
Gearbox Heater System
Kentucky Lock Tennessee River Basin Livingston County, Kentucky
Technical Specifications Ready to Advertise (RTA)
December 2021
THIS PAGE INTENTIONALLY LEFT BLANK
FOR DUPLEX PRINTING
Gearbox Heater System Kentucky Lock W912P522B0002 Ready to Advertise Livingston County, Kentucky
PROJECT TABLE OF CONTENTS
DI VI SI ON 01 - GENERAL REQUI REMENTS
01 00 00 GENERAL REQUIREMENTS
01 20 00 PRICE AND PAYMENT PROCEDURES
01 32 01.00 10 PROJECT SCHEDULE
01 33 00 SUBMITTAL PROCEDURES
01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS
01 35 50 PROJECT SITE SECURITY AND AT/OPSEC PROCEDURES
01 42 00 SOURCES FOR REFERENCE PUBLICATIONS
01 45 00.00 10 QUALITY CONTROL
01 45 00.15 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)
01 78 00 CLOSEOUT SUBMITTALS
01 78 23 OPERATION AND MAINTENANCE DATA
01 95 00 FORMS AND ATTACHMENTS
DI VI SI ON 26 - ELECTRI CAL
26 05 00 ELECTRICAL SUPPLY AND CONTROLS TO GEARBOX HEATERS
-- End of Project Table of Contents --
PROJECT TABLE OF CONTENTS Page 1
PROJECT TABLE OF CONTENTS Page 2
SECTION TABLE OF CONTENTS
DIVISION 01 - GENERAL REQUIREMENTS
SECTION 01 00 00
GENERAL REQUIREMENTS
PART 1 GENERAL
1.1 GENERAL
1.2 SCOPE OF WORK
1.3 REFERENCES
1.4 SUBMITTALS
1.5 WARRANTY
1.6 WORKING HOURS
1.6.1 Federal Holidays
1.7 CONSTRUCTION SEQUENCING
1.8 OCCUPANCY OF PREMISES
1.9 PERMITS AND LICENSES
1.10 SAFETY REQUIREMENTS
1.11 NON-COMPLIANCE OF SAFETY AND SECURITY REQUIREMENTS
1.12 PROTECTION OF EXISTING WORK AND DAMAGE REPORTS
1.13 CONTRACTOR'S STAGING AREA
1.14 SAFE CLEARANCE PROCEDURES
1.15 DAILY CLEANUP AND DISPOSAL
1.16 STORAGE OF EQUIPMENT AND MATERIALS
1.17 PROTECTION AND RESTORATION OF EXISTING FACILITIES
1.18 ENVIRONMENTAL PROTECTION
1.19 VETERANS EMPLOYMENT EMPHASIS FOR U.S. ARMY CORPS OF ENGINEERS
CONTRACTS
1.20 MEASUREMENT AND PAYMENT
PART 2 PRODUCTS
PART 3 EXECUTION
-- End of Section Table of Contents --
SECTION 01 00 00 Page 1
SECTION 01 00 00 Page 2
SECTION 01 00 00
GENERAL REQUIREMENTS
PART 1 GENERAL
1.1 GENERAL
This section comprises an explanation of the general contract requirements needed to accomplish the work. All work specified herein shall be accomplished in accordance with the procedures prescribed in the specifications and drawings.
1.2 SCOPE OF WORK
The scope of the work of this contract consists of the supply, installation, and testing at Kentucky Lock of all new power circuits and controls for existing gearboxes as shown on the contract drawings.
Heater controls shall be installed only within downstream recesses where plug heater for each gearbox is currently available.
1.3 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)
ER 385-1-31 (2009) The Control of Hazardous Energy
1.4 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.
SD-01 Preconstruction Submittals
Construction Sequence; G, ECD-E
1.5 WARRANTY
The Contractor must provide the Government a one year warranty from the date of final acceptance by the Contracting Officer's Representative (COR), and comply with applicable warranty requirements of Section 01 78 00 CLOSEOUT SUBMITTALS. The one year warranty period shall start after each completed, in-place item of work has been tested in accordance with the technical specifications and accepted by the Government. The warranty must cover defective materials, design and workmanship. In instances where the material or equipment manufacturer's advertised minimum warranty is in excess of one year, it must remain in force for its full period. Upon
SECTION 01 00 00 Page 3 receipt of notice from the Contracting Officer of failure of any of the material or equipment during the warranty period, the Contractor must promptly furnish and install new replacement parts at no additional cost to the Government.
1.6 WORKING HOURS
Normal working hours are Monday through Thursday 6:30 AM to 5:00 PM CST.
Work must be scheduled around federal holidays. Any exceptions must be approved by the COR. Submit requests to change work hours at least 14 calendar days in advance of need.
1.6.1 Federal Holidays
Do not schedule work on Federal holidays
a. 2022 Federal Holiday Schedule
Date Holiday Friday, December 31 New Year's Day Monday, January 17 MLK Day Monday, February 21* Washington's Birthday Monday, May 30 Memorial Day Monday, June 20** Juneteenth National Independence Day Monday, July 4 Independence Day Monday, September 5 Labor Day Monday, October 10 Columbus Day Friday, November 11 Veterans Day Thursday, November 24 Thanksgiving Day Monday, December 26*** Christmas Day
*This holiday is designated as "Washington's Birthday" in section 6103(a) of title 5 of the United States Code, which is the law that specifies holidays for Federal employees. Though other institutions such as state and local governments and private businesses may use other names, it is our policy to always refer to holidays by the names designated in the law.
**June 19, 2021 (the legal Federal holiday for Juneteenth National Independence Day), falls on a Sunday. Monday, June 20, will be treated as a Federal holiday.
***December 25, 2021 (the legal Federal holiday for Christmas), falls on a Sunday, Monday December 26, will be treated as a Federal holiday.
1.7 CONSTRUCTION SEQUENCING
Submit the construction sequence for approval to make sure the gearbox heaters and removal conductors must not interfere not only daily operations of lock personnel but in addition to ongoing construction at the new Kentucky Lock addition. Contractor must coordinate with Contracting Officer to ensure any temporary electrical outages or usage does not in anyway delay or affect construction at new lock.
1.8 OCCUPANCY OF PREMISES
Kentucky Lock will be operating during performance of the work under this Contract.
SECTION 01 00 00 Page 4
Before work is started, the Contractor must arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches and roadways.
1.9 PERMITS AND LICENSES
The Contractor must, at his/her own expense, obtain any licenses, permits or bonding required to perform the contract. The Contractor must comply with current federal, state, and local laws and regulations and must comply with any subsequent changes.
1.10 SAFETY REQUIREMENTS
The Contractor must comply with all applicable provisions of EM 385-1-1 Safety and Health Requirements Manual and Section 01 35 26 GOVERNMENTAL
SAFETY REQUIREMENTS.
1.11 NON-COMPLIANCE OF SAFETY AND SECURITY REQUIREMENTS
If the Contractor fails or refuses to promptly comply with the safety and security requirements, the COR may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to any such stoppage shall be made subject to claim for extension of time or for excess costs or damages to the Contractor. The Contractor will not be paid for work not performed as a result of the stop order. Work shall not resume until the Contractor provides evidence to the COR that he/she has complied or will comply with appropriate safety and security regulations.
1.12 PROTECTION OF EXISTING WORK AND DAMAGE REPORTS
In all instances when Government property and/or equipment is damaged by the Contractor's employees or any contract employees, the Contractor shall immediately suspend all work, and notify the COR. A full written report of the incident including the extent of damage shall be submitted to the COR for evaluation within two workdays of occurrence. The Contractor shall wait for a Notification to Proceed from the COR before resuming any work activities.
1.13 CONTRACTOR'S STAGING AREA
The Contractor will be assigned an area within or near the project site for use as a staging area. The building of structures, the erection of tents or other forms of protection will be permitted only at such places as the Government shall approve, and the sanitary conditions of the grounds in or about such structures shall at all times be maintained in a satisfactory manner. Temporary Contractor facilities provided during site operations shall be removed prior to final acceptance from the Government. As a minimum the area shall be left looking "broom clean" and at least as clean as before the structure placement.
1.14 SAFE CLEARANCE PROCEDURES
Project personnel use a Safe Clearance System, as stated in ER 385-1-31 and amended by the Nashville District to ensure continuity of service and safety to personnel and equipment. Any work performed which requires taking the Project's operating equipment out of service will be done only after a formal clearance is obtained by the Contracting Officer with 48-hour minimum notice. Contractor personnel shall not violate clearance.
SECTION 01 00 00 Page 5
Any violation of Safe Clearance Procedures will be grounds for removal of the offender(s). Copies of the Nashville District Safe Clearance Procedure will be supplied to the Contractor upon request.
1.15 DAILY CLEANUP AND DISPOSAL
Work areas shall be kept reasonably neat on a daily basis. Debris resulting from the work, such as empty paint cans, packing cases, scrap lumber, oil and grease spills, and other debris shall be collected, removed, and disposed of off-site at least once per week. Government trash cans, dump boxes and other containers shall not be used. Liquid waste shall not be disposed of in existing drains.
1.16 STORAGE OF EQUIPMENT AND MATERIALS
Storage of equipment and materials will be permitted only in designated staging areas.
1.17 PROTECTION AND RESTORATION OF EXISTING FACILITIES
Existing facilities shall be protected whether or not shown on the drawings. Upon completion of the work, existing facilities, not included as a portion of the work, shall be left in a condition equal to the original condition prior to the contract. Costs for repair and restoration of any facilities shall be considered to be incidental to and included in the contract price.
1.18 ENVIRONMENTAL PROTECTION
Contractor must maintain all work within and outside the project boundaries free from environmental pollution that would be in violation of any federal, state, local regulations or permits.
1.19 VETERANS EMPLOYMENT EMPHASIS FOR U.S. ARMY CORPS OF ENGINEERS
CONTRACTS
In addition to complying with the requirements outlined in FAR Part 22.13 EQUAL OPPORTUNITY FOR VETERANS, FAR Clause 52.222-35 EQUAL OPPORTUNITY FOR VETERANS, FAR Clause 52.222-37 EMPLOYMENT REPORTS ON VETERANS, DFARS
222.13 SPECIAL DISABLED AND VIETNAM ERA VETERANS, and Department of Labor regulations, U.S. Army Corps of Engineers (USACE) contractors and subcontractors at all tiers are encouraged to promote the training and employment of U.S. veterans while performing under a USACE contract.
While no set-aside, evaluation preference, or incentive applies to the solicitation or performance under the resultant contract, USACE contractors are encouraged to seek out highly qualified veterans to perform services under this contract. The following resources are available to assist USACE contractors in their outreach efforts:
a. U.S. Department of Labor Veterans employment: https://www.dol.gov/vets/
b. Federal veteran employment information: www.fedshirevets.gov/index.aspx
c. Veterans Opportunity to Work (VOW) Program: http://benefits.va.gov/vow/
d. U.S. Army Warrior Transition Command Employment Index:
https://wct.army.mil/modules/employers/index.html
SECTION 01 00 00 Page 6 http://www.wct.army.mil/modules/employers/index.html
d. Hiring Our Heroes initiative:
www.uschamberfoundation.org/hiring-our-heroes
1.20 MEASUREMENT AND PAYMENT
No separate payment will be made for the work covered under this section, except as otherwise provided. The costs thereof shall be included in the item to which the work pertains. Payment for the work required under this contract will made as listed in the bidding schedule and as described in Section 01 20 00 PRICE AND PAYMENT PROCEDURES.
PART 2 PRODUCTS
Not Used.
PART 3 EXECUTION
Not Used.
-- End of Section --
SECTION 01 00 00 Page 7
SECTION 01 00 00 Page 8
SECTION TABLE OF CONTENTS
DIVISION 01 - GENERAL REQUIREMENTS
SECTION 01 20 00
PRICE AND PAYMENT PROCEDURES
PART 1 GENERAL
1.1 PAYMENT ITEMS
1.1.1 Performance and Payment Bonds
1.1.1.1 Payment
1.1.1.2 Unit of Measure
1.1.2 Electrical Work
1.1.2.1 Payment
1.1.2.2 Unit of Measure
PART 2 PRODUCTS
PART 3 EXECUTION
3.1 CONTRACT COST BREAKDOWN
SECTION 01 20 00 Page 1
SECTION 01 20 00 Page 2
SECTION 01 20 00
PRICE AND PAYMENT PROCEDURES
PART 1 GENERAL
1.1 PAYMENT ITEMS
Payment items for the work required under this contract are listed in the BIDDING SCHEDULE and described below. All costs for items of work, which are not specifically mentioned to be included in a particular payment item, shall be included in the listed item most closely associated with the work involved. Payment made for each item listed shall constitute full compensation for furnishing all plant, labor, materials, and equipment,tools, supplies, and incidentals necessary to complete the work, 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 Performance and Payment Bonds
1.1.1.1 Payment
Payment will be made for the performance and payment bonds that are required as part of this contract. The Government will pay the actual cost of acceptable performance and payment bonds or the Contractor's bid price, whichever is less. The Contractor shall provide evidence of payment (paid invoice) from the bonding company or agency. If the actual cost of the bonds is less than the line item amount, the contract will be modified to adjust the line item accordingly. Adjustment(s) to the line item will also be made for any revisions to the actual bond costs associated with contract changes.
1.1.1.2 Unit of Measure
Unit of measure: Job.
1.1.2 Electrical Work
1.1.2.1 Payment
Payment will be made for costs associated with operations necessary for providing power to gearbox heaters. New electrical work consists of the installment of all new cable, conduit, safety switches, combination heater contactor, system testing and verification, drilling and chipping, and all other items necessary to complete the work in compliance with the plans and specifications.
1.1.2.2 Unit of Measure
Unit of measure: Job.
SECTION 01 20 00 Page 3
PART 2 PRODUCTS
Not Used
PART 3 EXECUTION
3.1 CONTRACT COST BREAKDOWN
The Contractor must furnish within 30 days after the date of Notice to Proceed, and prior to the submission of its first partial payment estimate, a breakdown of its single job pay item or items which will be reviewed by the Contracting Officer as to propriety of distribution of the total cost to the various accounts. Any unbalanced items as between early and late payment items or other discrepancies will be revised by the Contracting Officer to agree with a reasonable cost of the work included in the various items. This contract cost breakdown will then be utilized as the basis for progress payments to the Contractor.
SECTION 01 20 00 Page 4
SECTION TABLE OF CONTENTS
DIVISION 01 - GENERAL REQUIREMENTS
SECTION 01 32 01.00 10
PROJECT SCHEDULE
PART 1 GENERAL
1.1 REFERENCES
1.2 SUBMITTALS
1.3 PROJECT SCHEDULER QUALIFICATIONS
PART 2 PRODUCTS
2.1 SOFTWARE
2.1.1 Contractor Software
2.1.1.1 Primavera
PART 3 EXECUTION
3.1 GENERAL REQUIREMENTS
3.2 BASIS FOR PAYMENT AND COST LOADING
3.2.1 Activity Cost Loading
3.2.2 Withholdings / Payment Rejection
3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS
3.3.1 Level of Detail Required
3.3.2 Activity Durations
3.3.3 Procurement Activities
3.3.4 Mandatory Tasks
3.3.5 Government Activities
3.3.6 Contract Milestones and Constraints
3.3.6.1 Project Start Date Milestone
3.3.6.2 End Project Finish Milestone
3.3.6.3 Interim Completion Dates and Constraints
3.3.6.3.1 Start Phase
3.3.6.3.2 End Phase
3.3.7 Calendars
3.3.8 Open Ended Logic
3.3.9 Default Progress Data Disallowed
3.3.10 Out-of-Sequence Progress
3.3.11 Added and Deleted Activities
3.3.12 Original Durations
3.3.13 Leads, Lags, and Start to Finish Relationships
3.3.14 Retained Logic
3.3.15 Percent Complete
3.3.16 Remaining Duration
3.3.17 Cost Loading of Closeout Activities
3.3.17.1 As-Built Drawings
3.3.18 Anticipated Adverse Weather
3.3.19 Early Completion Schedule and the Right to Finish Early
3.4 PROJECT SCHEDULE SUBMISSIONS
3.4.1 Preliminary Project Schedule Submission
SECTION 01 32 01.00 10 Page 1
3.4.2 Initial Project Schedule Submission
3.4.3 Periodic Schedule Updates
3.5 SUBMISSION REQUIREMENTS
3.5.1 Narrative Report
3.5.2 Schedule Reports
3.5.2.1 Activity Report
3.5.2.2 Logic Report
3.5.2.3 Total Float Report
3.5.2.4 Earnings Report by CLIN
3.5.3 Network Diagram
3.5.3.1 Continuous Flow
3.5.3.2 Project Milestone Dates
3.5.3.3 Critical Path
3.5.3.4 Banding
3.5.3.5 Cash Flow / Schedule Variance Control (SVC) Diagram
3.6 PERIODIC SCHEDULE UPDATE
3.6.1 Periodic Schedule Update Meetings
3.6.2 Update Submission Following Progress Meeting
3.7 WEEKLY PROGRESS MEETINGS
3.8 REQUESTS FOR TIME EXTENSIONS
3.8.1 Justification of Delay
3.8.2 Time Impact Analysis (Prospective Analysis)
3.8.3 Forensic Schedule Analysis (Retrospective Analysis)
3.8.4 Fragmentary Network (Fragnet)
3.8.5 Time Extension
3.8.6 Impact to Early Completion Schedule
3.9 FAILURE TO ACHIEVE PROGRESS
3.9.1 Artificially Improving Progress
3.9.2 Failure to Perform
3.9.3 Recovery Schedule
3.10 OWNERSHIP OF FLOAT
3.11 PRIMAVERA P6 MANDATORY REQUIREMENTS
SECTION 01 32 01.00 10 Page 2
SECTION 01 32 01.00 10
PROJECT SCHEDULE
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 29R-03 (2011) Forensic Schedule Analysis
AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction
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:
SD-01 Preconstruction Submittals
Project Scheduler Qualifications; G Preliminary Project Schedule; G Initial Project Schedule; G Periodic Schedule Update; G
1.3 PROJECT SCHEDULER QUALIFICATIONS
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 all requirements of this specification.
2.1.1 Contractor Software
Scheduling software used by the contractor must be capable of meeting all
SECTION 01 32 01.00 10 Page 3 requirements of this specification.
2.1.1.1 Primavera
If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.
PART 3 EXECUTION
3.1 GENERAL REQUIREMENTS
Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. 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. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules.
Prepare each Project Schedule using the Precedence Diagram Method (PDM).
3.2 BASIS FOR PAYMENT AND COST LOADING
The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN.
3.2.1 Activity Cost Loading
Activity cost loading must be reasonable and without front-end loading.
Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.
3.2.2 Withholdings / Payment Rejection
Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.
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.3 PROJECT SCHEDULE DETAILED REQUIREMENTS
3.3.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:
SECTION 01 32 01.00 10 Page 4
3.3.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.
3.3.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.3.4 Mandatory Tasks
Include the following activities/tasks in the initial project schedule and all updates.
a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each).
b. Submission, review and acceptance of features require design completion
c. Long procurement activities
d. Submission and approval of as-built drawings.
e. Contractor's pre-final inspection.
f. Correction of punch list from Contractor's pre-final inspection.
g. Government's pre-final inspection.
h. Correction of punch list from Government's pre-final inspection.
i. Final inspection.
SECTION 01 32 01.00 10 Page 5
3.3.5 Government Activities
Show Government and other agency activities that could impact progress.
These activities include, but are not limited to: approvals, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.
3.3.6 Contract Milestones and Constraints
Milestone activities are to be used for significant project events 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.
3.3.6.1 Project Start Date Milestone
The first activity in the project schedule must be a start milestone titled "NTP Acknowledged,"
3.3.6.2 End Project Finish Milestone
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.3.6.3 Interim Completion Dates and Constraints
3.3.6.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.3.6.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.3.7 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, concrete cure times, 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 days provided in the contract clause TIME EXTENSIONS FOR UNUSUALLY SEVERE
SECTION 01 32 01.00 10 Page 6
WEATHER. 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.3.8 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.3.9 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.3.10 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.3.11 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.3.12 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.3.13 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 7
3.3.14 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.3.15 Percent Complete
Update the percent complete for each activity started, based on the realistic assessment of earned value. 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.3.16 Remaining Duration
Update the remaining duration for each activity based on the number of estimated work days it will take to complete the activity. Remaining duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete.
3.3.17 Cost Loading of Closeout Activities
Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) 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 correction of all punch list work identified during Government pre-final inspection(s).
3.3.17.1 As-Built Drawings
If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than $35,000 or 1 percent of the present contract value, which ever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's approval.
3.3.18 Anticipated Adverse Weather
Paragraph applicable to contracts with clause entitled TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.
3.3.19 Early Completion Schedule and the Right to Finish Early
An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required contract work will be completed before the contractually required completion date.
a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.
b. The Government is under no obligation to accelerate work items it is
SECTION 01 32 01.00 10 Page 8 responsible for to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.
3.4 PROJECT SCHEDULE SUBMISSIONS
Provide the submissions as described below. The reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.
Review comments made by the Government on the schedule(s) do not relieve the Contractor from compliance with requirements of the Contract Documents.
3.4.1 Preliminary Project Schedule Submission
Within 15 calendar days after the NTP is acknowledged submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).
3.4.2 Initial Project Schedule Submission
Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. No payment will be made for work items not fully detailed in the Project Schedule.
3.4.3 Periodic Schedule Updates
Update the Project Schedule on a regular basis, monthly at a minimum.
Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS. These updates will enable the Government to assess Contractor's progress.
a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.
SECTION 01 32 01.00 10 Page 9
b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.
3.5 SUBMISSION REQUIREMENTS
Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:
3.5.1 Narrative Report
Provide a Narrative Report with each schedule submission. 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.
Include the following information as minimum in the Narrative Report:
a. Identify and discuss the work scheduled to start in the next update period.
b. A description of activities along the two most critical paths where the total float is less than or equal to 20 work days.
c. 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.
d. Identify and explain why activities based on their calculated late dates should have either started or finished during the update period but did not.
e. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was 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.
f. Identify and discuss out-of-sequence work.
3.5.2 Schedule Reports
The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer. Typically, reports contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format. The following lists typical reports that will be requested:
3.5.2.1 Activity Report
List of all activities sorted according to activity number.
3.5.2.2 Logic Report
List of detailed predecessor and successor activities for every activity in ascending order by activity number.
SECTION 01 32 01.00 10 Page 10
3.5.2.3 Total Float Report
A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.
3.5.2.4 Earnings Report by CLIN
A compilation of the Total Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following 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.5.3 Network Diagram
The Network Diagram is required for the Preliminary, Initial and Periodic Updates. Depict and display 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.5.3.1 Continuous Flow
Show a continuous flow from left to right with no arrows from right to left. Show the activity number, description, duration, and estimated earned value on the diagram.
3.5.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.5.3.3 Critical Path
Show all activities on the critical path. The critical path is defined as the longest path.
3.5.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.5.3.5 Cash Flow / Schedule Variance Control (SVC) Diagram
With each schedule submission, provide a SVC diagram showing 1) Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates, and 2) Earned Value to-date.
SECTION 01 32 01.00 10 Page 11
3.6 PERIODIC SCHEDULE UPDATE
3.6.1 Periodic Schedule Update Meetings
Conduct periodic schedule update meetings for the purpose of reviewing the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and progress payment. Conduct meetings at least monthly within five days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows all meeting participants to view the proposed schedule during the meeting. The Contractor's authorized scheduler must organize, group, sort, filter, perform schedule revisions as needed and review functions as requested by the Contractor and/or Government. The meeting is a working interactive exchange which allows the Government and Contractor the opportunity to review the updated schedule on a real time and interactive basis. The meeting will last no longer than 8 hours. Provide a draft of the proposed narrative report and schedule data file to the Government a minimum of two workdays in advance of the meeting. The Contractor's Project Manager and scheduler must attend the meeting with the authorized representative of the Contracting Officer. Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work.
Following the periodic schedule update meeting, make corrections to the draft submission. Include only those changes approved by the Government in the submission and invoice for payment.
3.6.2 Update Submission Following Progress Meeting
Submit the complete Periodic Schedule Update of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 work days after the periodic schedule update meeting.
3.7 WEEKLY PROGRESS MEETINGS
Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled PERIODIC SCHEDULE UPDATE MEETINGS 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. 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.
3.8 REQUESTS FOR TIME EXTENSIONS
Provide a justification of delay to the Contracting Officer in accordance with the contract provisions and clauses for approval within 10 days of a delay occurring. Also prepare a time impact analysis for each Government request for proposal (RFP) to justify time extensions.
3.8.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). Evaluate multiple impacts chronologically; each with its own justification of delay. With multiple
SECTION 01 32 01.00 10 Page 12 impacts consider any concurrence 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.8.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.8.3 Forensic Schedule Analysis (Retrospective Analysis)
Prepare an analysis for approval by the Contracting Officer based on industry standard AACE 29R-03 .
3.8.4 Fragmentary Network (Fragnet)
Prepare a proposed fragnet for time impact analysis consisting 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. The proposed fragnet must be approved by the Contracting Officer prior to incorporation into the project schedule.
3.8.5 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.8.6 Impact to Early Completion Schedule
No extended overhead will be paid for delay prior to the original Contract 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.
3.9 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 provision of a written recovery plan for
SECTION 01 32 01.00 10 Page 13 approval. 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.9.1 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 plan must be evident at the work site and documented in the daily report along with the Schedule Narrative Report.
3.9.2 Failure to Perform
Failure to perform work and maintain progress in accordance with the supplemental recovery plan may result in an interim and final unsatisfactory performance rating and/or may result in corrective action directed by the Contracting Officer pursuant to FAR 52.236-15 Schedules for Construction Contracts, FAR 52.249-10 Default (Fixed-Price Construction), and other contract provisions.
3.9.3 Recovery Schedule
Should the Contracting Officer find it necessary, submit a recovery schedule pursuant to FAR 52.236-15 Schedules for Construction Contracts.
3.10 OWNERSHIP OF FLOAT
Except for the provision given in the paragraph IMPACT TO EARLY COMPLETION SCHEDULE, float available in the schedule, at any time, may 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.11 PRIMAVERA P6 MANDATORY REQUIREMENTS
If Primavera P6 is being used, request a backup file template (.xer) from the Government, if one is available, prior to building the schedule. The following settings are mandatory and required in all schedule submissions to the Government:
a. Activity Codes must be Project Level, not Global or EPS level.
b. Calendars must be Project Level, not Global or Resource level.
c. Activity Duration Types must be set to "Fixed Duration & Units" .
d. Percent Complete Types must be set to "Physical".
e. Time Period Admin Preferences 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.
SECTION 01 32 01.00 10 Page 14
f. Set Schedule Option for defining Critical Activities to "Longest Path".
g. Set Schedule Option for defining progressed activities to "Retained Logic".
h. Set up cost loading using a single lump sum labor 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.
i. Activity ID's must not exceed 10 characters.
j. Activity Names must have the most defining and detailed description within the first 30 characters.
SECTION 01 32 01.00 10 Page 15
SECTION 01 32 01.00 10 Page 16
SECTION TABLE OF CONTENTS
DIVISION 01 - GENERAL REQUIREMENTS
SECTION 01 33 00
SUBMITTAL PROCEDURES
PART 1 GENERAL
1.1 SUMMARY
1.1.1 Submittal Information
1.1.2 Submission of Submittals
1.2 DEFINITIONS
1.2.1 Submittal Descriptions (SD)
1.2.2 Approving Authority
1.2.3 Work
1.3 SUBMITTALS
1.4 SUBMITTAL CLASSIFICATION
1.4.1 Government Approved (G)
1.4.2 For Information Only
1.5 PREPARATION
1.5.1 Transmittal Form
1.5.2 Submittal Format
1.5.2.1 Format of SD-01 Preconstruction Submittals
1.5.2.2 Format for SD-02 Shop Drawings
1.5.2.2.1 Drawing Identification
1.5.2.3 Format of SD-03 Product Data
1.5.2.3.1 Product Information
1.5.2.3.2 Standards
1.5.2.3.3 Data Submission
1.5.2.4 Format of SD-04 Samples
1.5.2.4.1 Sample Characteristics
1.5.2.4.2 Sample Incorporation
1.5.2.4.3 Comparison Sample
1.5.2.5 Format of SD-05 Design Data
1.5.2.6 Format of SD-06 Test Reports
1.5.2.7 Format of SD-07 Certificates
1.5.2.8 Format of SD-08 Manufacturer's Instructions
1.5.2.8.1 Standards
1.5.2.9 Format of SD-09 Manufacturer's Field Reports
1.5.2.10 Format of SD-10 Operation and Maintenance Data (O&M)
1.5.2.11 Format of SD-11 Closeout Submittals
1.5.3 Source Drawings for Shop Drawings
1.5.3.1 Source Drawings
1.5.3.2 Terms and Conditions
1.5.4 Electronic File Format
1.6 QUANTITY OF SUBMITTALS
1.6.1 Number of SD-01 Preconstruction Submittal Copies
1.6.2 Number of SD-04 Samples
1.7 INFORMATION ONLY SUBMITTALS
1.8 PROJECT SUBMITTAL REGISTER
1.8.1 Submittal Management
1.8.2 Preconstruction Use of Submittal Register
SECTION 01 33 00 Page 1
1.8.3 Contractor Use of Submittal Register
1.8.4 Approving Authority Use of Submittal Register
1.8.5 Action Codes
1.8.5.1 Contractor Action Codes
1.8.6 Delivery of Copies
1.9 VARIATIONS
1.9.1 Considering Variations
1.9.2 Proposing Variations
1.9.3 Warranting that Variations are Compatible
1.9.4 Review Schedule Extension
1.10 SCHEDULING
1.11 GOVERNMENT APPROVING AUTHORITY
1.11.1 Review Notations
1.12 DISAPPROVED SUBMITTALS
1.13 APPROVED SUBMITTALS
1.14 APPROVED SAMPLES
1.15 WITHHOLDING OF PAYMENT
1.16 STAMPS
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 .