FCPSA RTA Spec.pdf
PDF 3 MB Posted
- Attached to
- COVERED PARKING ARRAY AT FARMINGDALE AFRC
- Solicitation number
- W912DS26BA004
About this file
This document is a detailed technical specification for a solar photovoltaic (PV) system and electric vehicle (EV) charging infrastructure project at the Farmingdale Armed Forces Reserve Center (AFRC) in New York. The project involves constructing two tubular steel canopy structures to support solar panels, installing an integrated gutter and stormwater drainage system, a premanufactured battery storage building, and four dual-port EV charging stations.
The technical specification provides comprehensive requirements for the solar PV system, including detailed specifications for photovoltaic modules, inverters, combiner boxes, monitoring systems, and grounding equipment. The system is designed to be grid-connected with a minimum rated output of 120-130 kW DC and AC, mounted on parking canopies. Key technical specifications include monocrystalline PV module requirements, string inverter efficiency, system monitoring capabilities, and comprehensive testing and commissioning protocols. The project also includes specific requirements for installation, safety, labeling, warranties, and post-installation training for government personnel.
View the file
Other files
Show all 11
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
AFRC FARMINGDALE COVERED
PARKING SOLAR ARRAY PROJECT
Contract # W912DS19D0009
QPK Design Project # 222281
UNITED STATES ARMY CORPS OF ENGINEERS
RTA SPECIFICATIONS 25 APRIL 2025
AFRC Farmingdale Covered Parking Solar Array W912DS19D0009
PROJECT TABLE OF CONTENTS
DIVISION 01 - GENERAL REQUIREMENTS
01 11 00 02/24 SUMMARY OF WORK
01 14 00 11/22, CHG 3: 08/24 WORK RESTRICTIONS
01 20 00 11/20, CHG 4: 08/24 PRICE AND PAYMENT PROCEDURES
01 30 00 11/20, CHG 4: 08/24 ADMINISTRATIVE REQUIREMENTS
01 32 01.00 10 08/23, CHG 1: 08/24 PROJECT SCHEDULE
01 33 00 08/18, CHG 4: 02/21 SUBMITTAL PROCEDURES
01 35 26 05/24 GOVERNMENTAL SAFETY REQUIREMENTS
01 42 00 05/24 SOURCES FOR REFERENCE PUBLICATIONS
01 45 00 08/23, CHG 1: 05/24 QUALITY CONTROL
01 45 00.15 10 11/23 RESIDENT MANAGEMENT SYSTEM CONTRACTOR
MODE (RMS CM)
01 45 35 05/24 SPECIAL INSPECTIONS
01 50 00 11/20, CHG 3: 08/24 TEMPORARY CONSTRUCTION FACILITIES AND
CONTROLS
01 58 00 08/19, CHG 5: 08/22 PROJECT IDENTIFICATION
01 74 19 02/19, CHG 3: 11/21 CONSTRUCTION WASTE MANAGEMENT AND
DISPOSAL
01 78 00 05/19, CHG 1: 08/21 CLOSEOUT SUBMITTALS
01 78 23 05/23 OPERATION AND MAINTENANCE DATA
DIVISION 03 - CONCRETE
03 30 00 02/19, CHG 8: 05/24 CAST-IN-PLACE CONCRETE
DIVISION 05 - METALS
05 12 00 08/18, CHG 2: 05/21 STRUCTURAL STEEL
DIVISION 09 - FINISHES
09 96 00 11/14 HIGH-PERFORMANCE COATINGS
DIVISION 11 - EQUIPMENT
11 11 37 11/18 ELECTRIC VEHICLE SUPPLY EQUIPMENT
DIVISION 13 - SPECIAL CONSTRUCTION
13 34 23 08/20, CHG 1: 02/21 PREFABRICATED UTILITY BUILDING
DIVISION 26 - ELECTRICAL
26 05 73 08/23 POWER SYSTEM STUDIES
26 20 00 08/23 INTERIOR DISTRIBUTION SYSTEM
26 31 00 11/21 FACILITY-SCALE SOLAR PHOTOVOLTAIC (PV)
SYSTEMS
26 51 00 05/20, CHG 2: 11/21 INTERIOR LIGHTING
26 56 00 08/21 EXTERIOR LIGHTING
DIVISION 31 - EARTHWORK
31 00 00 08/23 EARTHWORK
31 05 19.13 02/21 GEOTEXTILES FOR EARTHWORK
31 63 29 11/19 DRILLED CONCRETE PIERS AND SHAFTS
PROJECT TABLE OF CONTENTS Page 1
DIVISION 32 - EXTERIOR IMPROVEMENTS
32 01 19.61 11/19 SEALING OF JOINTS IN RIGID PAVEMENT
32 11 20 05/22 BASE MATERIAL FOR RIGID AND FOR
FLEXIBLE PAVING
32 11 26 05/20 HOT-MIX BITUMINOUS BASE COURSE FOR
ROADS AND STREETS
32 12 13 05/24 BITUMINOUS TACK AND PRIME COATS
32 12 16.16 11/20 ROAD-MIX ASPHALT PAVING
32 16 19 05/18 CONCRETE CURBS, GUTTERS AND SIDEWALKS
32 17 23 08/16, CHG 5: 11/18 PAVEMENT MARKINGS
32 92 19 08/17 SEEDING
DIVISION 33 - UTILITIES
33 40 00 11/21 STORMWATER UTILITIES
-- End of Project Table of Contents --
PROJECT TABLE OF CONTENTS Page 2
SECTION 01 11 00
SUMMARY OF WORK
02/24
PART 1 GENERAL
1.1 FAR 52.211-10 COMMENCEMENT, PROSECUTION AND COMPLETION OF WORK
a. The Contractor is required to (i) commence work under this contract within five (5) calendar days after the date the Contractor receives the Notice to Proceed, (ii) prosecute the work diligently, and (iii) complete the entire work ready for use, not later than 692 calendar days after the date the Contractor receives the notice to proceed. The time stated for completion must include the final cleanup of the premises.
b. The Contractor must furnish all labor, materials, equipment, and services for the following work as described in the construction documents.
c. All work must be in accordance with the drawings and specifications or instructions attached hereto and made a part thereof, or to be furnished hereafter by the Contracting Officer and subject, in every detail, to his supervision, direction, and instructions
1.2 WORK COVERED BY CONTRACT DOCUMENTS
1.2.1 Project Description
The work includes canopy structures constructed of tubular steel to provide a framework of support for the array of solar panels. To capture water an integral gutter system will be installed to collect water that drains between solar panels. This water will be directed to the storm water system. There are two canopy structures that will be located at the north edge of the POV parking area. The foundations will be in the grass area outside of the pavement area to minimize impact to the parking surface. A premanufactured building is also to house the batteries. The design of the battery storage building is aesthetically pleasing and will coordinate with the site features. Four charging stations, each station having the capability to charge two vehicles. Refer to the electrical and structural descriptions for additional information.at the north edge of the Privately Owned Vehicle (POV) parking area adjacent to the Gatehouse off Baiting Place Road and to the north of the main building.Contractor to adjust layout due to differences in panel size proposed to achieve similar detailing and look provided in drawings.
SECTION 01 11 00 Page 1
1.3 DISCLOSURE OF THE MAGNITUDE OF CONSTRUCTION PROJECTS
This project is estimated between $1,000,000.00 and $5,000,000.00.
1.4 EXISTING WORK
Remove or alter existing sitework in such a manner as to prevent injury or damage to any portions of the existing work which remains.
Repair or replace portions of existing sitework that have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer. At the completion of operations, existing work must be in a condition equal to or better than that which existed before new work started.
1.5 LOCATION OF UNDERGROUND UTILITIES
Obtain digging permits prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities.
Contact local utility locating service a minimum of 48 hours prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work.
Identify and mark all other utilities not managed and located by the local utility companies. Scan the construction site with Ground Penetrating Radar (GPR), electromagnetic, or sonic equipment, and mark the surface of the ground or paved surface where existing underground utilities or utilities encased in structures are discovered. Verify the elevations of existing piping, utilities,and any type of underground or encased obstruction not indicated, or specified to be removed, that is indicated or discovered during scanning, in locations to be traversed by piping, ducts, and other work to be conducted or installed. Verify elevations before installing new work closer than nearest manhole or other structure at which an adjustment in grade can be made.
1.5.1 Notification Prior to Excavation
Notify the Contracting Officer at least 15 days prior to starting excavation work.
PART 2 PRODUCTS
Not used.
PART 3 EXECUTION
Not used.
-- End of Section --
SECTION 01 11 00 Page 2
SECTION 01 14 00
WORK RESTRICTIONS
11/22, CHG 3: 08/24
PART 1 GENERAL
1.1 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.
Submit the following in accordance with Section 01 33 00 SUBMITTAL
PROCEDURES:
SD-01 Preconstruction Submittals
List of Contact Personnel
1.2 CONTRACTOR ACCESS AND USE OF PREMISES
1.2.1 Activity Regulations
Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear appropriate personal protective equipment (PPE) in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Ensure all Contractor equipment, include delivery vehicles, are clearly identified with their company name.
1.2.1.1 Subcontractors and Personnel Contacts
Provide a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.
1.2.1.2 No Smoking Policy
Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.
1.2.2 Working Hours
Regular working hours will consist of an 8 1/2 hour period established by the Contracting Officer, between 7 a.m. and 3:30 p.m., excluding Government holidays.
1.2.3 Work Outside Regular Hours
Work outside regular working hours requires Contracting Officer approval.
Make application 15 calendar days prior to such work to allow arrangements
SECTION 01 14 00 Page 1 to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title. Based on the justification provided, the Contracting Officer may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer.
1.2.4 Exclusionary Period
No work, including deliveries may be performed during the period listed belowwithout prior written approval of the Contracting Officer. These periods have not been considered in computing the time allowed for the performance of this contract.
a. All Government Holidays: Eleven (11) days per Calendar year.
b. The Contractor should anticipate six (6) additional days each calendar year on which no physical work must be performed. These will be at the Governments discretion. The actual "No Work" days will be confirmed by the Government during the work phase in conjunction with the construction plan approval. The Contractor's schedule must reflect the above anticipated "no work" days. These dates ARE considered in computing the time allowed for the performance of this contract.
1.2.5 Utility Cutovers and Interruptions
a. Make utility cutovers and interruptions after normal working hours or on Saturdays, Sundays, and Government holidays. Conform to procedures required in paragraph WORK OUTSIDE REGULAR HOURS.
b. Ensure that new utility lines are complete, except for the connection, before interrupting existing service.
c. Interruption to water, sanitary sewer, storm sewer, telephone service, electric service, air conditioning, heating, fire alarm, compressed air, and are considered utility cutovers pursuant to the paragraph
WORK OUTSIDE REGULAR HOURS.
d. Operation of Station Utilities: The Contractor must not operate nor disturb the setting of control devices in the station utilities system, including water, sewer, electrical, and steam services. The Government will operate the control devices as required for normal conduct of the work. The Contractor must notify the Contracting Officer giving reasonable advance notice when such operation is required.
PART 2 PRODUCTS
Not used.
PART 3 EXECUTION
Not used.
SECTION 01 14 00 Page 2
SECTION 01 20 00
PRICE AND PAYMENT PROCEDURES
11/20, CHG 4: 08/24
PART 1 GENERAL
1.1 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.
Submit the following in accordance with Section 01 33 00 SUBMITTAL
PROCEDURES:
1.2 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.
1.3 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.
SECTION 01 20 00 Page 1
SECTION 01 20 00 Page 2
SECTION 01 30 00
ADMINISTRATIVE REQUIREMENTS
11/20, CHG 4: 08/24
PART 1 GENERAL
1.1 REFERENCES
The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.
U.S. ARMY CORPS OF ENGINEERS (USACE)
EM 385-1-1 (2024) Safety -- Safety and Occupational Health (SOH) Requirements
1.2 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.
Submit the following in accordance with Section 01 33 00 SUBMITTAL
PROCEDURES:
1.3 MINIMUM INSURANCE REQUIREMENTS
Provide the minimum insurance coverage required by FAR 28.307-2 Liability, during the entire period of performance under this contract. Provide other insurance coverage as required by New York State law.
1.3.1 Work on a Government Installation
a. Before commencing work under this contract, the Contractor must notify the Contracting Officer in writing that the required insurance has been obtained. The policies evidencing required insurance must contain an endorsement to the effect that cancellation or material change adversely affecting the Government's interest cannot be effective for such a period as may be prescribed by the laws of the State in which this contract is to be performed and in no event less than 30 days after written notice thereof to the Contracting Officer.
b. The Contractor must insert the substance of this clause, including this paragraph (b), in subcontracts under this contract that require work on a Government installation and must require subcontractors to provide and maintain the insurance required in the Schedule or elsewhere in the contract. The Contractor must maintain a copy of all subcontractors' proofs of required insurance, and must make copies available to the Contracting Officer upon request.
c. This insurance will be included at no additional cost to the government.
SECTION 01 30 00 Page 1
1.4 SUPERVISION
1.4.1 Superintendent Qualifications
Provide project superintendent with 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 may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.
1.4.2 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.4.3 Duties
The project superintendent is primarily responsible for managing subcontractors and coordinating day-to-day production and schedule adherence on the project. The superintendent is required to attend Red Zone meetings, 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.4.4 Non-Compliance Actions
The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to ensure timely completion.
Furthermore, the Contracting Officer 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.
1.5 PRECONSTRUCTION CONFERENCE
prior to commencing any work at the site, coordinate with the Contracting Officer a time and place to meet for the Preconstruction Conference . The purpose of this conference is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to: daily reporting, invoicing, value engineering, safety, base-access, outage requests, hot work permits, schedule requirements, quality control, schedule of prices or earned value report, shop drawings, submittals, cybersecurity, prosecution of the work, government acceptance, final inspections and contract close-out. Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.
SECTION 01 30 00 Page 2
The Contractor must provide at this conference the following items as indicated:
a. Initial Project Schedule; Section 01 32 01.00 10 PROJECT SCHEDULE.
b. Accident Prevention Plan (APP); Section 01 35 26 GOVERNMENTAL SAFETY
REQUIREMENTS
c. Contractor Quality Control (CQC) Plan; Section 01 45 00 QUALITY CONTROL.
d. List of Contact Personnel; Section 01 14 00 WORK RESTRICTIONS.
e. Letter appointing Superintendent.
f. Detailed Concept of Operations Plan.
No other Government representative is authorized to accept such requests.
A copy must also be provided to the Authorized Representative of the Contracting Officer.
Provide the Contracting Officer with a copy of any requests for additional time, money or interpretation of contract requirements which were provided to the Authorized Representative of the Contracting Officer and which have not been resolved after 90 days
1.5.1 Attendees
Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.
The Contractor's provision and use of an electronic payroll processing system must meet the following basic functional criteria: commercially available; compliant with appropriate Davis Bacon Act payroll provisions in the FAR; able to accommodate the required numbers of employees and subcontractors planned to be employed under the contract; demonstrated security of data and data entry rights; ability to produce Contractor-certified electronic versions of weekly payroll data; ability to identify erroneous entries and track the data/time of all versions of the certified Davis Bacon payrolls submitted to the government over the life of the contract; capable of generating a durable record copy, that is, a CD or DVD and PDF file record of data from the system database at end of the contract closeout. This durable record copy of data from the electronic Davis-Bacon payroll processing system must be provided to the Government during contract closeout.
All Contractor-incurred costs related to the Contractor's provision and use of an electronic payroll processing service must be included in the Contractor's price for the overall work under the contract. The costs for Davis-Bacon Act compliance using electronic payroll processing services must not be a separately bid/proposed or reimbursed item under this contract.
1.5.2 Submission of Claims
The following must be submitted to the Contracting Officer at the following address: U.S. Army Corps of Engineers, Room 16- 300, New York District, 26 Federal Plaza, New York, New York 10278-0090:
SECTION 01 30 00 Page 3
a. Claims referencing or mentioning the Contracting Disputes Act of 1978.
b. Requests for a written decision by the Contracting Officer.
c. Claims certified in accordance with the Contract Disputes Act of 1978.
The Contractor is encouraged to use a commercially-available electronic system to process and submit certified payrolls electronically to the Government. The requirements for preparing, processing and providing certified labor payrolls are established by the Davis-Bacon Act as stated in FAR 52.222-8, PAYROLLS AND BASIC RECORDS and FAR 52.222-13, COMPLIANCE WITH DAVIS-BACON AND RELATED ACT REGULATIONS.
If the Contractor elects to use an electronic Davis-Bacon payroll processing system, then the Contractor must be responsible for obtaining and providing for all access, licenses, and other services required to provide for receipt, processing, certifying, electronically transmitting to the Government and storing weekly payroll and other services required for the Contractor to comply with Davis Bacon and related Act regulations.
When the Contractor uses an electronic Davis-Bacon payroll system, the electronic payroll service must be used by the Contractor to prepare, process, and maintain the relevant payrolls and basic records during all work under this construction contract and the electronic payroll service must be capable of preserving these payrolls and related basic records for the required three years after contract completion. If the Contractor chooses to use an electronic Davis- Bacon payroll system, then the Contractor must obtain and provide electronic system access to the Government, as required to comply with the Davis-Bacon and related Act regulations over the duration of this construction contract. The access must include electronic review access by the Government contract administration office to the electronic payroll processing system used by the Contractor.
The Contractor's provision and use of an electronic payroll processing system must meet the following basic functional criteria: commercially available; compliant with appropriate Davis Bacon Act payroll provisions in the FAR; able to accommodate the required numbers of employees and subcontractors planned to be employed under the contract; capable of producing an Excel spreadsheet-compatible electronic output of weekly payroll records (format at http://www.rmssupport.com/guides.aspx) for export in an Excel spreadsheet to be imported into the Contractor's Quality Control System (QCS) version of RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM), that in turn must export payroll data to the Government's RESIDENT MANAGEMENT SYSTEM (RMS); demonstrated security of data and data entry rights; ability to produce Contractor- certified electronic versions of weekly payroll data; ability to identify erroneous entries and track the data/time of all versions of the certified Davis Bacon payrolls submitted to the government over the life of the contract;
capable of generating a durable record copy, that is, a CD or DVD and PDF file record of data from the system database at end of the contract closeout. This durable record copy of data from the electronic Davis-Bacon payroll processing system must be provided to the Government during contract closeout.
All Contractor-incurred costs related to the Contractor's provision and use of an electronic payroll processing service must be included in the Contractor's price for the overall work under the contract. The costs for Davis-Bacon Act compliance using electronic payroll processing services
SECTION 01 30 00 Page 4 must not be a separately bid/proposed or reimbursed item under this contract.
1.5.3 DESIGNATION OF PROPERTY ADMINISTRATOR
The Chief, Property and Accounting Section, U.S. Army Engineer District, New York, Federal Building, 26 Federal Plaza, New York, N.Y. 10278-0090 is designated as Property Administrator, in connection with this contract.
1.6 FACILITY TURNOVER PLANNING MEETINGS (Red Zone Meetings)
Meet with the Government to identify strategies to ensure the project is carried to expeditious closure and turnover to the Client. Start planning the turnover process at the Pre-Construction Conference meeting with a discussion of the Red Zone process and convene at regularly scheduled Red Zone Meetings beginning at approximately 75 percent of project completion. Include the following in the facility Turnover effort:
1.6.1 Red Zone Checklist
a. Contracting Officer's Technical Representative (COTR) will provide the Contractor a copy of the Red Zone Checklist template.
b. Prior to 75 percent completion, modify the Red Zone Checklist template by adding or deleting critical activities applicable to the project and assign planned completion dates for each activity. Submit the modified Red Zone Checklist to the Contracting Officer. The Contracting Officer may request additional activities be added to the Red Zone Checklist at any time as necessary.
1.6.2 Meetings
a. Conduct regular Red Zone Meetings beginning at approximately 75 percent project completion, or three to six months prior to Beneficial Occupancy Date (BOD), whichever comes first.
b. The Contracting Officer will establish the frequency of the meetings, which is expected to increase as the project completion draws nearer.
At the beginning, Red Zone meetings may be every two weeks then increase to weekly towards the final month of the project.
c. Using the Red Zone Checklist as a Plan of Action and Milestones (POAM) and basis for discussion, review upcoming critical activities and strategies to ensure work is completed on time.
d. During the Red Zone Meetings discuss with the COTR any upcoming activities that require Government involvement.
e. Maintain the Red Zone Checklist by documenting the actual completion dates as work is completed and update the Red Zone Checklist with revised planned completion dates as necessary to match progress.
Distribute copies of the current Red Zone Checklist to attendees at each Red Zone Meeting.
SECTION 01 30 00 Page 5
PART 2 PRODUCTS
Not used.
PART 3 EXECUTION
Not used.
SECTION 01 30 00 Page 6
SECTION 01 32 01.00 10
PROJECT SCHEDULE
08/23, CHG 1: 08/24
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
AACE 84R-13 (2015) Planning and Accounting for Adverse Weather
AMERICAN SOCIETY OF CIVIL ENGINEERS (ASCE)
ASCE 67-17 (2017) Schedule Delay Analysis
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" or "S" classification. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.
Submit the following in accordance with Section 01 33 00 SUBMITTAL
PROCEDURES:
SD-01 Preconstruction Submittals
Project Scheduler Qualifications
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 Designated Project Scheduler must have prepared and maintained at least three previous construction schedules for projects of similar size and complexity to this contract, using Primavera P6..
Representative must have a comprehensive knowledge of CPM scheduling
SECTION 01 32 01.00 10 Page 1 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 Government Default Software
The Government uses Primavera P6. Ensure exported schedule files are compatible with the version of P6 used by the Government.
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. Verify at the SEKO meeting which version of P6 is in use by the Government. Export the schedule in a version of P6 no newer than that used by the Government.
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.
PART 3 EXECUTION
3.1 GENERAL REQUIREMENTS
Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 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.1.1 Scheduling Expectations Kickoff Meeting(SEKO)
In conjunction with the post award conference or pre construction conference the Government and the Contractor will hold a separate and
SECTION 01 32 01.00 10 Page 2 distinct Scheduling Expectations Kickoff Meeting(SEKO). The intent of this meeting is for the Government to review with the contractor the requirements of the scheduling specification, communicate the Government’s expectations regarding schedule development and management, and answer any questions the Contractor may have regarding the schedule requirements.
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. Match the progress payment "Pay Period Thru" date in RMS to the schedule data date.
3.2.1 Activity Cost Loading
Activity cost loading must be reasonable and without front-end loading.
Activities with a negative cost loading is not allowed. Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.
3.2.2 Cost Loading of Submittals
No costs are to be assigned to activities for the preparation, review, or approval of submittals, except as described under paragraph COST LOADING OF CLOSEOUT ACTIVITIES, paragraph AS-BUILT DRAWINGS, and paragraph O&M
MANUALS.
3.2.3 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.
Non-procurement activities Original Durations (OD) are not to exceed 20 workdays or 30 calendar days.
SECTION 01 32 01.00 10 Page 3
3.3.3 Procurement Activities
Include in the schedule 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 Activities
Include the following activities in the initial project schedule and all updates.
a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each).
Submission, review and acceptance of features requiring design completion Submission, review and acceptance of design packages.
b. Submission of electrical systems layout drawings.
c. Submission and approval of O & M manuals.
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.
3.3.5 Government Activities
Show in schedule, Government and other agency activities that could impact progress. These activities include, but are not limited to 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.
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
SECTION 01 32 01.00 10 Page 4
Field Activity Code Length Description
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 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.
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, SECTION 01 32 01.00 10 Page 5 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 Number (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 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.
Mandatory constraints that ignore or affect 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.
SECTION 01 32 01.00 10 Page 6
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.
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 Adverse Weather
Ensure anticipated adverse weather is accounted for in the Project Schedule. AACE 84R-13 provides methodologies for techniques in planning for adverse weather. The preferred methodology is the use of a weather calendar. If a method other than a weather calendar is proposed, discuss the reason during the SEKO meeting.
3.3.9 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 a weather calendar is used its implementation and execution is to be in accordance with AACE 84R-13
3.3.10 Open Ended Logic
Only two open ended activities are allowed: the first activity "NTP Acknowledged" is to have no predecessor logic, and the last activity -"End Project" is to have no successor logic. Except as noted above, each activity must have at least a start-to-start or finish-to-start relationship with its predecessor and a finish-to-finish or finish-to-start relationship with its successor.
SECTION 01 32 01.00 10 Page 7
Predecessor open ended logic may be allowed in a time impact analyses upon the Contracting Officer's approval.
3.3.11 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.12 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.13 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.14 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.15 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 or create float, or to replace proper schedule logic.
a. Leads (negative lags) are prohibited.
b. Start to Finish (SF) relationships are prohibited.
3.3.16 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.
SECTION 01 32 01.00 10 Page 8
3.3.17 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. Budgeted cost of activity is to be reduced by the amount needed to correct deficiency. The activity referenced in paragraph COST LOADING of CLOSEOUT ACTIVITIES must have its budgeted cost increased by this amount.
3.3.18 Remaining Duration
Update the remaining duration for each activity based on the number of estimated workdays it will take to complete the activity. Remaining duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete. The remaining duration for unstarted activities are not to be less than its orginal duration.
3.3.19 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.19.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.19.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.20 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.
3.4 PROJECT SCHEDULE SUBMISSIONS
Provide the submissions as described below. The data reports and network
SECTION 01 32 01.00 10 Page 9 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, 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. Code activities that are summary in nature, after the first 90 calendar days, with the following activity codes: 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…
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 .