Draft - Division 1 - Bettis 100 QC Specs.pdf
PDF 2 MB Posted
- Solicitation number
- W911WN27R0005
About this file
This is a 100% Quality Control Technical Specifications document for Division 1 General Requirements of the AT Courtyard Construction project at Bettis Laboratory in West Mifflin, Pennsylvania, dated November 2026 (Draft status).
The specifications establish comprehensive administrative and technical requirements for construction management, including project scheduling using Critical Path Method (CPM) with Primavera P6 software, quality control procedures, safety compliance per EM 385-1-1 (2024), and submittal requirements. Key contract payment items include Site Preparation and Demolition, Concrete, Earthwork, Bioretention Area and Site Furnishings, Raised Seating Area and Landscaping, and Site Utilities, all structured as single job payment items. The contractor must designate a qualified project superintendent with minimum 10 years construction experience (5 as superintendent on similar projects) and a project scheduler with 2+ years experience in construction scheduling. Major administrative requirements include submission of a Preliminary Project Schedule within 15 calendar days of Notice to Proceed and an Initial Project Schedule within 42 calendar days, with monthly periodic updates required thereafter. Submittal procedures mandate use of ENG Form 4025 and electronic submission through the Resident Management System (RMS), with submittals classified as either Government-approved ("G" designation) or for information only. Specific cost-loading requirements apply to closeout activities, including minimum $35,000–$200,000 for as-built drawings and $20,000 for O&M manuals. The specifications require preconstruction conferences, informal partnering sessions, weekly progress meetings, and strict compliance with schedule logic, activity coding per Standard Data Exchange Format (SDEF), and calendar development accommodating weather delays and seasonal work restrictions.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Draft - Technical Specs - Bettis 100 QC Specs.pdf | ||
| UAA Information Form (1).pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AT COURTYARD
Bettis Laboratory West Mifflin, Pennsylvania
100% QC
Technical Specifications November 2026
DRAFT
PROJECT TABLE OF CONTENTS
DIVISION 01 - GENERAL REQUIREMENTS
01 11 00 SUMMARY OF WORK
01 20 00.00 08 PRICE AND PAYMENT PROCEDURES
01 30 00.00 08 ADMINISTRATIVE REQUIREMENTS
01 32 01.00 08 PROJECT SCHEDULE NETWORK ANALYSIS
01 33 00 SUBMITTAL PROCEDURES
01 35 00.00 08 SPECIAL PROCEDURES
01 35 26.00 08 GOVERNMENTAL SAFETY REQUIREMENTS
01 42 00 SOURCES FOR REFERENCE PUBLICATIONS
01 45 00.00 08 QUALITY CONTROL
01 45 00.15 10 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)
01 45 00.25 10 CONSTRUCTION MANAGEMENT PLATFORM (CMP)
01 57 19.00 08 TEMPORARY ENVIRONMENTAL CONTROLS
01 57 23.00 08 STORMWATER POLLUTION PREVENTION MEASURES
01 78 02.00 08 CLOSEOUT SUBMITTALS (AS-BUILT DRAWINGS)
-- End of Project Table of Contents --
PROJECT TABLE OF CONTENTS Page 1
100% QC
SECTION TABLE OF CONTENTS
DIVISION 01 - GENERAL REQUIREMENTS
SECTION 01 11 00
SUMMARY OF WORK
PART 1 GENERAL
1.1 SUBMITTALS
1.2 WORK COVERED BY CONTRACT DOCUMENTS
1.2.1 Project Description
1.2.2 Location
PART 2 PRODUCTS
PART 3 EXECUTION
-- End of Section Table of Contents --
SECTION 01 11 00 Page 1
SECTION 01 11 00
SUMMARY OF WORK
PART 1 GENERAL
1.1 SUBMITTALS
Government approval is required for submittals with a "G" classification.
Submittals not having a "G" lassification 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:
1.2 WORK COVERED BY CONTRACT DOCUMENTS
1.2.1 Project Description
The work includes the work being completed at the Bettis AT Courtyard. To prepare the site for the new work, the contractor will be demolishing the existing water, storm, and gas lines, pavement, safety fencing, and concrete barriers. New landscaping, decorative concrete, furnishings, and utillites are to be installed in the courtyard area.
1.2.2 Location
The work is located at the Bettis Laboratory, approximately as indicated.
The exact location will be shown by the Contracting Officer.
PART 2 PRODUCTS
Not used.
PART 3 EXECUTION
Not used.
-- End of Section --
SECTION 01 11 00 Page 2
DIVISION 01 - GENERAL REQUIREMENTS
SECTION 01 20 00.00 08
PRICE AND PAYMENT PROCEDURES
PART 1 GENERAL
1.1 SINGLE JOB PAYMENT ITEMS
1.1.1 Site Preperation and Demolition
1.1.1.1 Payment
1.1.1.2 Unit of Measure
1.1.1.3 Payment Item (s)
1.1.2 Concrete
1.1.2.1 Payment
1.1.2.2 Unit of Measure
1.1.2.3 Payment Item (s)
1.1.3 Earthwork
1.1.3.1 Payment
1.1.3.2 Unit of Measure
1.1.3.3 Payment Item (s)
1.1.4 Bioretention Area and Site Furnishings
1.1.4.1 Payment
1.1.4.2 Unit of Measure
1.1.4.3 Payment Item (s)
1.1.5 Raised Seating Area and Landscaping
1.1.5.1 Payment
1.1.5.2 Unit of Measure
1.1.5.3 Payment Item (s)
1.1.6 Site Utilities
1.1.6.1 Payment
1.1.6.2 Unit of Measure
1.1.6.3 Payment Item (s)
PART 2 PRODUCTS
PART 3 EXECUTION
3.1 CONTRACT COST BREAKDOWN
-- End of Section Table of Contents --
SECTION 01 20 00.00 08 Page 1
SECTION 01 20 00.00 08
PRICE AND PAYMENT PROCEDURES
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 Site Preperation and Demolition
1.1.1.1 Payment
Payment will be made for costs associated with site preperation and demolition as indicated on the contract drawings. All traffic mats, utility protection, erosion and sediment controls, site excavation, hauling, and demolition work and all other incidental costs in connection with these aspects of the work under this contract.
1.1.1.2 Unit of Measure
Unit of measure: Job.
1.1.1.3 Payment Item (s)
0001 SITE PREPERATION AND DEMOLITION
1.1.2 Concrete
1.1.2.1 Payment
Payment for these items shall constitute full compensation for all labor, equipment, material and supply costs for performing the work, as indicated on the contract drawings, including: concrete footers, concrete banding, concrete paving, all required reinforcing bars, brick veneer installation, subbase and aggregate for concrete work, expansion joints, and all other miscellaneous concrete.
1.1.2.2 Unit of Measure
Unit of measure: Job.
SECTION 01 20 00.00 08 Page 2
1.1.2.3 Payment Item (s)
0002 CONCRETE
1.1.3 Earthwork
1.1.3.1 Payment
Payment for these items shall constitute full compensation for all labor, equipment, material and supply costs for performing the work, as indicated on the contract drawings, including: clearing and grubbing, soil testing, miscellanous excavation, fine grading, trenching, pipe bedding, compacting, and hauling spoils.
1.1.3.2 Unit of Measure
Unit of measure: Job.
1.1.3.3 Payment Item (s)
0003 EARTHWORK
1.1.4 Bioretention Area and Site Furnishings
1.1.4.1 Payment
Payment for these items shall constitute full compensation for all labor, equipment, material and supply costs for performing the work, as indicated on the contract drawings, including: complete bioretention area, outdoor furniture, and the pergola.
1.1.4.2 Unit of Measure
Unit of measure: Job.
1.1.4.3 Payment Item (s)
0004 BIORETENTION AREA AND SITE FURNISHINGS
1.1.5 Raised Seating Area and Landscaping
1.1.5.1 Payment
Payment for these items shall constitute full compensation for all labor, equipment, material and supply costs for performing the work, as indicated on the contract drawings, including: complete raised seating area, groundcover planting, mulch, deciduous trees, shrubs, and perennials.
1.1.5.2 Unit of Measure
Unit of measure: Job.
1.1.5.3 Payment Item (s)
0005 RAISED SEATED AREA AND LANDSCAPING
SECTION 01 20 00.00 08 Page 3
1.1.6 Site Utilities
1.1.6.1 Payment
Payment for these items shall constitute full compensation for all labor, equipment, material and supply costs for performing the work, as indicated on the contract drawings, including: storm, sanitary, water, and gas lines, a complete storm system, and all miscellaneous fittings
1.1.6.2 Unit of Measure
Unit of measure: Job.
1.1.6.3 Payment Item (s)
0006 SITE UTILITIES
PART 2 PRODUCTS
Not Used
PART 3 EXECUTION
3.1 CONTRACT COST BREAKDOWN
The Contractor must furnish within 30 calendar 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 or designated representative as to propriety of distribution of the total cost to the various accounts. The cost of any element in the cost breakdown should be less than $25,000 for progress tracking. Any unbalanced items as between early and late payment items or other discrepancies will be revised by the Contracting Officer or designated representative 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.
-- End of Section --
SECTION 01 20 00.00 08 Page 4
DIVISION 01 - GENERAL REQUIREMENTS
SECTION 01 30 00.00 08
ADMINISTRATIVE REQUIREMENTS
PART 1 GENERAL
1.1 SUMMARY
1.2 REFERENCES
1.3 ACRONYMS
1.4 CONTRACT ADMINISTRATION
1.5 USACE ACQUISITION INSTRUCTIONS (UAI)
1.5.1 UAI 5122.1302-100 VETERANS EMPLOYMENT EMPHASIS FOR U.S. ARMY
CORPS OF ENGINEERS CONTRACTS
1.6 SUPERVISION
1.6.1 Minimum Communication Requirements
1.6.2 Superintendent Qualifications
1.6.2.1 Duties
1.6.3 Non-Compliance Actions
1.7 PRECONSTRUCTION CONFERENCE
1.8 PARTNERING
1.8.1 Informal Partnering
PART 2 PRODUCTS
PART 3 EXECUTION
-- End of Section Table of Contents --
SECTION 01 30 00.00 08 Page 1
SECTION 01 30 00.00 08
ADMINISTRATIVE REQUIREMENTS
PART 1 GENERAL
1.1 SUMMARY
This section contains contract administrative requirements which are not covered in Section 00 70 00 CONDITIONS OF THE CONTRACT or Section 00 73 00
SUPPLEMENTARY CONDITIONS.
1.2 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 (2024) Safety -- Safety and Occupational Health (SOH) Requirements
1.3 ACRONYMS
DFARS - Defense Federal Acquisition Regulation Supplement EP - Engineer Pamphlet FAR - Federal Acquisition Regulation SAT - Simplified Acquisition Threshold UAI - USACE Acquisition Instruction
1.4 CONTRACT ADMINISTRATION
An Administrative Contracting Officer (ACO) will be designated on this contract to act within the limits delegated by the Contracting Officer.
The ACO designation letter will clearly detail what the authorities of the
ACO.
1.5 USACE ACQUISITION INSTRUCTIONS (UAI)
1.5.1 UAI 5122.1302-100 VETERANS EMPLOYMENT EMPHASIS FOR U.S. ARMY CORPS
OF ENGINEERS CONTRACTS
In addition to complying with the requirements outlined in FAR Part 22.13, FAR Provision 52.222-38, FAR Clause 52.222-35, FAR Clause 52.222-37, DFARS
222.13 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:
U.S. Department of Labor Veterans’ Employment and Training Service
SECTION 01 30 00.00 08 Page 2
(VETS): https://www.dol.gov/vets/
Federal Veteran Employment Information: https://www.fedshirevets.gov/
Veterans Opportunity to Work (VOW) Program:
https://www.benefits.va.gov/vow/
Army Recovery Care Program: https://www.arcp.army.mil/
Hiring Our Heroes:
https://www.uschamberfoundation.org/hiring-our-heroes
1.6 SUPERVISION
1.6.1 Minimum Communication Requirements
Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of contract work. In addition, if a Quality Control (QC) representative is required on the contract, then that individual must also have fluent English communication skills.
1.6.2 Superintendent Qualifications
The project superintendent must have a minimum of 10 years experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Contracting Officer or designated representative may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question. The project superintendent may not serve as the CQC System Manager or the Site Safety and Health Officer (SSHO).
1.6.2.1 Duties
The project superintendent is primarily responsible for managing and coordinating day-to-day production and schedule adherence on the project.
The superintendent is required to attend partnering meetings, and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.
1.6.3 Non-Compliance Actions
The Project Superintendent is subject to removal by the Contracting Officer or designated representative for non-compliance with requirements specified in the contract and for failure to manage the project to insure timely completion. Furthermore, the Contracting Officer or designated representative 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 such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.
SECTION 01 30 00.00 08 Page 3
1.7 PRECONSTRUCTION CONFERENCE
After award of the contract but prior to commencement of any work at the site, meet with the Contracting Officer or designated representative to discuss and develop a mutual understanding relative to the administration of the value engineering and safety program, preparation of the schedule of prices or earned value report, shop drawings, and other submittals, scheduling programming, prosecution of the work, clear expectations of the "Interim DD Form 1354" Submittal, and the processes for joint risk management between the Contractor and Government. Major Subcontractors who will engage in the work must also attend.
1.8 PARTNERING
To most effectively accomplish this contract, the Government requires the formation of a cohesive partnership within the Project Team whose members are from the Government, the Contractor and their Subcontractors. Key personnel from the Supported Command, the End User (who will occupy the facility), the Government Design and Construction team and Subject Matter Experts, the Installation, the Contractor and Subcontractors, and the Designer of Record will be invited to participate in the Partnering process. The Partnership will draw on the strength of each organization in an effort to achieve a project that is without any safety mishaps, conforms to the Contract, and stays within budget and on schedule.
The Contracting Officer or designated representative will provide information on the Informal Partnering Process and a list of key and optional personnel who should attend the Informal Partnering meeting.
1.8.1 Informal Partnering
The Contracting Officer or designated representative will organize the Informal Partnering Sessions with key personnel of the project team, including Contractor personnel and Government personnel.
The Initial Informal Partnering session should be a part of the Pre-Construction Meeting. Informal Partnering sessions will be held at a location agreed to by the Contracting Officer or designated representative and the Contractor (typically a conference room provided by the Resident Engineer office or the Contractor). The Initial Informal Partnering Session may be conducted and facilitated using electronic media (a video and accompanying forms) provided by the Contracting Officer or designated representative. The Partners will determine the frequency of the follow-on sessions, at no more than three to six month intervals.
PART 2 PRODUCTS
NOT USED
PART 3 EXECUTION
NOT USED
-- End of Section --
SECTION 01 30 00.00 08 Page 4
DIVISION 01 - GENERAL REQUIREMENTS
SECTION 01 32 01.00 08
PROJECT SCHEDULE NETWORK ANALYSIS
PART 1 GENERAL
1.1 REFERENCES
1.2 SUBMITTALS
1.3 PROJECT SCHEDULER QUALIFICATIONS
PART 2 PRODUCTS
2.1 SOFTWARE
2.1.1 Government Default Software
2.1.2 Contractor Software
2.1.2.1 Primavera
2.1.2.2 Other Than Primavera
PART 3 EXECUTION
3.1 GENERAL REQUIREMENTS
3.2 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 Standard Activity Coding Dictionary
3.3.6.1 Workers Per Day (WRKP)
3.3.6.2 Responsible Party Coding (RESP)
3.3.6.3 Area of Work Coding (AREA)
3.3.6.4 Modification Number (MODF)
3.3.6.5 Bid Item Coding (BIDI)
3.3.6.6 Phase of Work Coding (PHAS)
3.3.6.7 Category of Work Coding (CATW)
3.3.6.8 Feature of Work Coding (FOW)
3.3.7 Contract Milestones and Constraints
3.3.7.1 Project Start Date Milestone and Constraint
3.3.7.2 End Project Finish Milestone and Constraint
3.3.7.3 Interim Completion Dates and Constraints
3.3.7.3.1 Start Phase
3.3.7.3.2 End Phase
3.3.8 Calendars
3.3.9 Open Ended Logic
3.3.10 Default Progress Data Disallowed
3.3.11 Out-of-Sequence Progress
3.3.12 Added and Deleted Activities
SECTION 01 32 01.00 08 Page 1
3.3.13 Original Durations
3.3.14 Leads, Lags, and Start to Finish Relationships
3.3.15 Retained Logic
3.3.16 Percent Complete
3.3.17 Remaining Duration
3.3.18 Cost Loading of Closeout Activities
3.3.18.1 As-Built Drawings
3.3.18.2 O & M Manuals
3.3.19 Early Completion Schedule and the Right to Finish Early
3.4 PROJECT SCHEDULE SUBMISSIONS
3.4.1 Preliminary Project Schedule Submission
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.2.5 Schedule Log
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 TRANSFER OF SCHEDULE DATA INTO RMS/QCS
3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS
-- End of Section Table of Contents --
SECTION 01 32 01.00 08 Page 2
SECTION 01 32 01.00 08
PROJECT SCHEDULE NETWORK ANALYSIS
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
U.S. ARMY CORPS OF ENGINEERS (USACE)
ER 1-1-11 (2017) Administration -- Project Schedules
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, RO
Preliminary Project Schedule ; G, RO
Initial Project Schedule ; G, RO
Periodic Schedule Update ; G, RO
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.
SECTION 01 32 01.00 08 Page 3
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 Government Default Software
The Government intends to use Primavera P6.
2.1.2 Contractor Software
Scheduling software used by the Contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.
2.1.2.1 Primavera
If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.
2.1.2.2 Other Than Primavera
If the Contractor chooses software other than Primavera P6, that is compliant with this specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at project completion.
NOT USED
PART 3 EXECUTION
3.1 GENERAL REQUIREMENTS
Prepare for approval a Project Schedule, as specified herein, pursuant to Section 00 70 00 CONDITIONS OF THE CONTRACT, FAR 52.236-15 SCHEDULES 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.
SECTION 01 32 01.00 08 Page 4
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:
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. Submission of mechanical/electrical/information systems layout drawings.
SECTION 01 32 01.00 08 Page 5
d. Long procurement activities
e. Submission and approval of O & M manuals.
f. Submission and approval of as-built drawings.
g. Submission and approval of DD1354 data and installed equipment lists.
h. Submission and approval of testing and air balance (TAB).
i. Submission of TAB specialist design review report.
j. Submission and approval of fire protection specialist.
k. Submission and approval of Building Commissioning Plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with the contract commissioning requirements. All tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.
l. Air and water balancing.
m. Building commissioning - Functional Performance Testing.
n. Controls testing plan submission.
o. Controls testing.
p. Performance Verification testing.
q. Other systems testing, if required.
r. Contractor's pre-final inspection.
s. Correction of punch list from Contractor's pre-final inspection.
t. Government's pre-final inspection.
u. Correction of punch list from Government's pre-final inspection.
v. Final inspection.
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 Standard Activity Coding Dictionary
Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 . This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site:
http://rms.usace.army.mil .
SECTION 01 32 01.00 08 Page 6
100% QC
http://rms.usace.army.mil
The SDEF format is as follows:
Field Activity Code Length Description
1 WRKP 3 Workers per day
2 RESP 4 Responsible party
3 AREA 4 Area of work
4 MODF 6 Modification Number
5 BIDI 6 Bid Item (CLIN)
6 PHAS 2 Phase of work
7 CATW 1 Category of work
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.
3.3.6.1 Workers Per Day (WRKP)
Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.
3.3.6.2 Responsible Party Coding (RESP)
Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.
a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.
b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record);
ELEC (for the electrical Subcontractor); MECH (for the mechanical Subcontractor); and GOVT (for USACE).
3.3.6.3 Area of Work Coding (AREA)
Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew from working in more than one work area at a time due to
SECTION 01 32 01.00 08 Page 7 restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings.
Activities cannot have more than one Work Area Code.
Not all activities are required to be Work Area coded. A lack of Work Area coding indicates the activity is not resource or space constrained.
3.3.6.4 Modification Number (MODF)
Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.
3.3.6.5 Bid Item Coding (BIDI)
Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code.
3.3.6.6 Phase of Work Coding (PHAS)
Assign Phase of Work Code to all activities. Examples of phase of work are procurement phase and construction phase. Each activity can have only one Phase of Work code.
a. Code proposed fast track design and construction phases proposed to allow filtering and organizing the schedule by fast track design and construction packages.
b. If the contract specifies phasing with separately defined performance periods, identify a Phase Code to allow filtering and organizing the schedule accordingly.
3.3.6.7 Category of Work Coding (CATW)
Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to construction submittal, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.
3.3.6.8 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.
Definable Feature of Work is defined in Section 01 45 00.00 10 QUALITY CONTROL. An activity can have only one Feature of Work Code.
3.3.7 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.
SECTION 01 32 01.00 08 Page 8
Mandatory constraints that ignore or effect network logic are prohibited.
No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.
3.3.7.1 Project Start Date Milestone and Constraint
The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged.
3.3.7.2 End Project Finish Milestone and Constraint
The last activity in the schedule must be a finish milestone titled "End Project."
Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.
3.3.7.3 Interim Completion Dates and Constraints
Constrain contractually specified interim completion dates to show negative float when the calculated late finish date of the last activity in that phase is later than the specified interim completion date.
3.3.7.3.1 Start Phase
Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work.
3.3.7.3.2 End Phase
Use a finish milestone as the last activity for a project phase. Call the finish milestone "End Phase X" where "X" refers to the phase of work.
3.3.8 Calendars
Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop sSeasonal Calendar(s) and assign to seasonally affected activities as applicable.
If an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated adverse weather delay work days provided in the Special Contract. 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.
SECTION 01 32 01.00 08 Page 9
3.3.9 Open Ended Logic
Only two open ended activities are allowed: the first activity "NTP Acknowledged" may have no predecessor logic, and the last activity -"End Project" may have no successor logic.
Predecessor open ended logic may be allowed in a time impact analyses upon the Contracting Officer's approval.
3.3.10 Default Progress Data Disallowed
Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.
3.3.11 Out-of-Sequence Progress
Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer.
Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.
3.3.12 Added and Deleted Activities
Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.
3.3.13 Original Durations
Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.
3.3.14 Leads, Lags, and Start to Finish Relationships
Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb float, or to replace proper schedule logic.
a. Leads (negative lags) are prohibited.
b. Start to Finish (SF) relationships are prohibited.
3.3.15 Retained Logic
Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(s)
SECTION 01 32 01.00 08 Page 10 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.16 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.17 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.18 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.18.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.2 O & M Manuals
Cost load the "Submission and approval of O & M manuals" activity not less than $20,000. Activity will be declared 100 percent complete upon the Government's approval of all O & M manuals.
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 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.
SECTION 01 32 01.00 08 Page 11
3.4 PROJECT SCHEDULE SUBMISSIONS
Provide the submissions as described below. The data CD/DVD, 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 42calendar 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.
b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.
SECTION 01 32 01.00 08 Page 12
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.
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
SECTION 01 32 01.00 08 Page 13 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.2.5 Schedule Log
Provide a Scheduling/Leveling Report generated from the current project schedule being submitted.
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 08 Page 14
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 or designated representative in accordance with the contract provisions and clauses for approval within 10 calendar 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
SECTION 01 32 01.00 08 Page 15 chronologically; each with its own justification of delay. With multiple impacts consider any concurrency of delay. A time extension becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer or designated representative.
If the contractor foresees an impact or is currently being impacted to the schedule, they must add an activity to the schedule to represent the impact. This impact activity needs to be logically linked to all activities in the schedule that are being impacted including but not limited to the critical path activities. The impact activity must include the word "Impact" in the activity name.
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 .
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 .