C04_Attachment 2 USDA ARS SWRC Solar PH1 - Project Specification Manual.pdf

Project Manual

USDA AGRICULTURAL RESEARCH SERVICE

SWRC SOLAR PHASE 1

Southwest Watershed Research Center

2000 E. Allen Road, Tucson AZ 85719 prepared for:

Agricultural Research Service, Administrative and Financial Management

Pacific West Area Administrative Office

800 Buchanan Street, Albany, CA 94710 prepared by:

ajc architects

703 east 1700 south salt lake city, ut 84105

(801) 466-8818

March 2026 knielsen Text Box

100% CD

USDA Tucson Solar USDATUCSONSOLAR

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 02/24 SUMMARY OF WORK

a description of work covered in this contract and is required for use in all projects

01 14 00 11/22, CHG 3: 08/24 WORK RESTRICTIONS

work and site restrictions

01 20 00 11/20, CHG 4: 08/24 PRICE AND PAYMENT PROCEDURES

payment instruction paragraphs required for use in all projects

01 30 00 11/20, CHG 4: 08/24 ADMINISTRATIVE REQUIREMENTS

general administrative and procedural requirements for Contractor management and coordination

01 32 01.00 10 08/23, CHG 1: 08/24 PROJECT SCHEDULE

the preparation and maintenance of the project schedule for construction projects or design-build construction projects

01 32 16.00 20 08/18, CHG 1: 08/20 SMALL PROJECT CONSTRUCTION PROGRESS

SCHEDULES

the preparation and use of construction schedules for small projects

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

general procedures regarding submittals, data normally submitted for review to establish conformance with the design concept and contract documents

01 35 26 05/24 GOVERNMENTAL SAFETY REQUIREMENTS

safety and occupational health requirements for the protection of Contractor and Government personnel, property, and resources

01 42 00 05/24 SOURCES FOR REFERENCE PUBLICATIONS

listing of organizations whose publications are referenced in other sections of the specifications.

01 45 00 08/23, CHG 1: 05/24 QUALITY CONTROL

preparation and use of Design-Bid-Build (DBB) and Design-Build (DB) Quality Control

01 50 00 11/20, CHG 3: 08/24 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

temporary construction facilities, safety systems, construction traffic provisions, construction signage, jobsite Wi-Fi, and controls over Contractor operations required for use in all projects.

01 74 19 02/19, CHG 3: 11/21 CONSTRUCTION WASTE MANAGEMENT AND

DISPOSAL

the management of non-hazardous construction waste and demolition debris/waste materials

PROJECT TABLE OF CONTENTS Page 1

01 78 00 05/19, CHG 1: 08/21 CLOSEOUT SUBMITTALS

closeout submittals including: revised project documents, warranty management, testing, adjusting and balancing, O & M manuals, and cleanup

01 78 23 05/23 OPERATION AND MAINTENANCE DATA

Operation and Maintenance (O&M) data packages, manuals and training

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 92 00 08/23 JOINT SEALANTS

sealants for normal building construction

DIVISION 26 - ELECTRICAL

26 00 00.00 20 07/06 BASIC ELECTRICAL MATERIALS AND METHODS

electrical general requirements, complete

26 05 00.00 40 08/16 COMMON WORK RESULTS FOR ELECTRICAL

common to all electrical sections

26 05 48.00 10 10/07 SEISMIC PROTECTION FOR ELECTRICAL

EQUIPMENT

seismic protection of electrical equipment, conduit, and exterior utilities.

26 20 00 02/14 INTERIOR DISTRIBUTION SYSTEM

procurement, installation, and testing of electrical wiring systems for construction projects

26 31 00 11/21 FACILITY-SCALE SOLAR PHOTOVOLTAIC (PV)

SYSTEMS

facility-scale solar photovoltaic (PV) systems, and related equipment and materials

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 2

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 11 00

SUMMARY OF WORK

02/24 a description of work covered in this contract and is required for use in all projects

PART 1 GENERAL

1.1 SUBMITTALS

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

1.2.2 Location

1.3 OCCUPANCY OF PREMISES

1.4 EXISTING WORK

1.5 SALVAGE MATERIAL AND EQUIPMENT

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --

SECTION 01 11 00 Page 1

THIS PAGE INTENTIONALLY LEFT BLANK

SECTION 01 11 00 Page 2

SECTION 01 11 00

SUMMARY OF WORK

02/24

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submit the following in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Salvage Plan ; G

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The work includes Installation of new solar array on the existing building rooftop. Some patch and repair to the existing roof membrane will be performed due to the new panel attachments and incidental related work.

1.2.2 Location

The work is located at the UDSA ARS Southwest Watershed Research Center;

Tucson, Arizona , approximately as indicated. The exact location will be shown by the Contracting Officer.

1.3 OCCUPANCY OF PREMISES

Building(s) will be occupied during performance of work under this Contract. Occupancy notifications will be posted in a prominent location in the work area.

Before work is started, arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.

1.4 EXISTING WORK

Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work which remain.

Repair or replace portions of existing work which 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 SALVAGE MATERIAL AND EQUIPMENT

Items designated by the Contracting Officer to be salvaged remain the property of the Government. Segregate, itemize, deliver and off-load the salvaged property at the storage area located within 10 miles of the

SECTION 01 11 00 Page 3 construction site.

Provide a salvage plan , listing material and equipment to be salvaged, and their storage location. Maintain property control records for material or equipment designated as salvage. Provide a system for property control in the salvage plan. Store and protect salvaged materials and equipment until disposition by the Contracting Officer.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 4

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 14 00

WORK RESTRICTIONS

11/22, CHG 3: 08/24

work and site restrictions

PART 1 GENERAL

1.1 SUBMITTALS

1.2 CONTRACTOR ACCESS AND USE OF PREMISES

1.2.1 Activity Regulations

1.2.1.1 Subcontractors and Personnel Contacts

1.2.1.2 No Smoking Policy

1.2.2 Working Hours

1.2.3 Work Outside Regular Hours

1.2.4 Occupied Building

1.2.5 Utility Cutovers and Interruptions

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 14 00 Page 1

SECTION 01 14 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. Submit the following in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of Contact Personnel

SD-07 Certificates

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., Monday through Friday , , 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 3 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. Make utility cutovers after normal working hours or on Saturdays, Sundays, and Government holidays unless directed otherwise.

1.2.4 Occupied Building

The Contractor shall be working in an existing building around existing buildings which is occupied.

Provide dust covers or protective enclosures to protect existing work that remains, and Government material located in the building during the construction period.

Relocate movable furniture as required to perform the work, protect the furniture, and replace the furniture in its original location upon completion of the work. Leave attached equipment in place, and protect it against damage, or temporarily disconnect, relocate, protect, and reinstall it at the completion of the work.

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, are considered utility cutovers pursuant to the paragraph WORK

OUTSIDE REGULAR HOURS.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 14 00 Page 4

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 20 00

PRICE AND PAYMENT PROCEDURES

11/20, CHG 4: 08/24

payment instruction paragraphs required for use in all projects

PART 1 GENERAL

1.1 SUBMITTALS

1.2 CONTRACTOR'S INVOICE AND CONTRACT PERFORMANCE STATEMENT

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 20 00 Page 1

SECTION 01 20 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. Submit the following in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

1.2 CONTRACTOR'S INVOICE AND CONTRACT PERFORMANCE STATEMENT

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 20 00 Page 3

SECTION 01 20 00 Page 4

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

11/20, CHG 4: 08/24

general administrative and procedural requirements for Contractor management and coordination

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 VIEW LOCATION MAP

1.4 PROGRESS AND COMPLETION PICTURES

1.5 MINIMUM INSURANCE REQUIREMENTS

1.6 SUPERVISION

1.6.1 Superintendent Qualifications

1.6.2 Minimum Communication Requirements

1.6.3 Duties

1.6.4 Non-Compliance Actions

1.7 PRECONSTRUCTION

1.7.1 Attendees

1.8 FACILITY TURNOVER PLANNING MEETINGS (Red Zone Meetings)

1.8.1 Red Zone Checklist

1.8.2 Meetings

1.9 PARTNERING

1.9.1 Team-Led (Informal) Partnering

1.10 MOBILIZATION

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 30 00 Page 1

SECTION 01 30 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. Submit the following in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

View Location Map

Progress and Completion Pictures

1.3 VIEW LOCATION MAP

Submit, prior to or with the first digital photograph submittals, a sketch or drawing indicating the required photographic locations. Update as required if the locations are moved.

1.4 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color minimum resolution in JPEG file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten different viewpoints selected by the Contractor unless otherwise directed by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures.

Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file.

Include a date designator in file names. Photographs provided are for unrestricted use by the Government.

1.5 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage required by FAR 28.307-2 Liability, SECTION 01 30 00 Page 3 during the entire period of performance under this contract. Provide other insurance coverage as required by State law.

1.6 SUPERVISION

1.6.1 Superintendent Qualifications

Provide project superintendent with a minimum of 5 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.

For projects where the superintendent is permitted to also serve as the Quality Control (QC) Manager as established in Section 01 45 00 QUALITY CONTROL, the superintendent must have qualifications in accordance with that section.

1.6.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.6.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.6.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.7 PRECONSTRUCTION

prior to commencing any work at the site, coordinate with the Contracting Officer a time and place to meet for the Preconstruction. The purpose of this is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to:

SECTION 01 30 00 Page 4 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.

1.7.1 Attendees

Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.

1.8 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 NAVFAC Red Zone Meetings beginning at approximately 75 percent of project completion. Include the following in the facility Turnover effort:

1.8.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.8.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

1.9 PARTNERING

Host the partnering session within 45 calendar days of contract award. To most effectively accomplish this Contract, the Contractor and Government must form a cohesive partnership with the common goal of drawing on the strength of each organization in an effort to achieve a successful project without safety mishaps, conforming to the Contract, within budget and on schedule. The partnering team must consist of personnel from both the Government and Contractor including project level and corporate level leadership positions. Key Personnel from the supported command, end user, , Contractor, key subcontractors and the Designer of Record are required to participate in the Partnering process.

1.9.1 Team-Led (Informal) Partnering

a. The Contracting Officer will coordinate the initial Team-Led (Informal) Partnering Session with key personnel of the project team, including Contractor and Government personnel. The Partnering Session will be co-led by the Government Construction Manager and Contractor's Project Manager.

b. The Initial Team-led Partnering session may be held concurrently with the meeting. Partnering sessions will be held at a location mutually agreed to by the Contracting Officer and the Contractor, typically at a conference room on-base or at the Contractor's temporary trailer.

c. The Initial Team-Led Partnering Session will be conducted and facilitated using electronic media (a video and accompanying forms) provided by Contracting Officer.

d. The Partners will determine the frequency of the follow-on sessions.

e. Participants will bear their own costs for meals, lodging and transportation associated with Partnering.

1.10 MOBILIZATION

Contractor shall mobilize to the jobsite within 60 calendar days after contract award . Mobilize is defined as having equipment AND having a physical presence of at least one person from the contractor's team on the jobsite.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 30 00 Page 6

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

08/23, CHG 1: 08/24

the preparation and maintenance of the project schedule for construction projects or design-build construction projects

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.1.1 Scheduling Expectations Kickoff Meeting(SEKO)

3.2 BASIS FOR PAYMENT AND COST LOADING

3.2.1 Activity Cost Loading

3.2.2 Cost Loading of Submittals

3.2.3 Withholdings / Payment Rejection

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

3.3.2 Activity Durations

3.3.3 Design and Permit Activities

3.3.4 Procurement Activities

3.3.5 Mandatory Activities

3.3.6 Government Activities

3.3.7 Standard Activity Coding Dictionary

3.3.7.1 Workers Per Day (WRKP)

3.3.7.2 Responsible Party Coding (RESP)

3.3.7.3 Area of Work Coding (AREA)

3.3.7.4 Modification Number (MODF)

3.3.7.5 Bid Item Coding (BIDI)

3.3.7.6 Phase of Work Coding (PHAS)

3.3.7.7 Category of Work Coding (CATW)

3.3.7.8 Feature of Work Coding (FOW)

3.3.8 Contract Milestones and Constraints

3.3.8.1 Project Start Date Milestone and Constraint

3.3.8.2 End Project Finish Milestone and Constraint

3.3.8.3 Interim Completion Dates and Constraints

SECTION 01 32 01.00 10 Page 1

3.3.8.3.1 Start Phase

3.3.8.3.2 End Phase

3.3.9 Adverse Weather

3.3.10 Calendars

3.3.11 Open Ended Logic

3.3.12 Default Progress Data Disallowed

3.3.13 Out-of-Sequence Progress

3.3.14 Added and Deleted Activities

3.3.15 Original Durations

3.3.16 Leads, Lags, and Start to Finish Relationships

3.3.17 Retained Logic

3.3.18 Percent Complete

3.3.19 Remaining Duration

3.3.20 Cost Loading of Closeout Activities

3.3.20.1 As-Built Drawings

3.3.20.2 O & M Manuals

3.3.21 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.2.1 Design Package Schedule Submission

3.4.3 Periodic Schedule Updates

3.5 SUBMISSION REQUIREMENTS

3.5.1 Electronic Scheduling Data

3.5.2 Narrative Report

3.5.3 Schedule Reports

3.5.3.1 Activity Report

3.5.3.2 Logic Report

3.5.3.3 Total Float Report

3.5.3.4 Earnings Report by CLIN

3.5.3.5 Scheduling and Leveling Report

3.5.4 Network Diagram

3.5.4.1 Continuous Flow

3.5.4.2 Project Milestone Dates

3.5.4.3 Critical Path

3.5.4.4 Grouping and Sorting

3.5.4.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 Changes That Do Not Cause Delay

3.8.3 Time Impact Analysis (Prospective Analysis)

3.8.4 Forensic Schedule Analysis (Retrospective Analysis)

3.8.5 Fragmentary Network (Fragnet)

3.8.6 Time Extension

3.8.7 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 RESIDENT MANAGEMENT SYSTEM

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

SECTION 01 32 01.00 10 Page 2

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 Contractor Quality Control approval. 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 ; G, Preliminary Project Schedule ; G, Initial Project Schedule ; G, Periodic Schedule Update ; G,

1.3 PROJECT SCHEDULER QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The Designated Project Scheduler must have prepared and maintained at least three previous construction schedules for projects of

SECTION 01 32 01.00 10 Page 3 similar size and complexity to this contract, using Primavera P6..

Representative must have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

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

2.1.1 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 design and construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Designers, 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).

SECTION 01 32 01.00 10 Page 4

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 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, design submittals, 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:

Procurement time: Estimates are 12 weeks for PV equipment.

Construction Work Installation time to Complete:

a. CLIN1: 1 (one)month(s)

SECTION 01 32 01.00 10 Page 5

b. CLIN2: 1 (one)month(s) Test & Balance time: 5 (Five) Day(s) Commission / Startup time: 5 (Five) Day(s) Turnover time to CLIN1: 4.5 month(s).

Total Construction Time: 6.5 months

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.

3.3.3 Design and Permit Activities

Include design and permit activities with the necessary conferences and follow-up actions and design package submission dates. Include the design schedule in the project schedule, showing the sequence of events involved in carrying out the project design tasks within the specific contract period. Provide a detailed level of scheduling sufficient to identify all major design tasks, including those that control the flow of work. Also include review and correction periods associated with each item.

3.3.4 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.5 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).

b. Submission, review and acceptance of features requiring design completion Submission, review and acceptance of design packages.

c. Submission of mechanical/electrical/information systems layout drawings. d. Submission and approval of O & M manuals.

e. Submission and approval of as-built drawings.

f. Submission and approval of DD1354 data and installed equipment lists.

g. Submission and approval of testing and air balance (TAB).

h. Submission of TAB specialist design review report.

i. Submission and approval of fire protection specialist.

j. Submission and approval of Building Commissioning Plan, Controls testing plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a

SECTION 01 32 01.00 10 Page 6 level of detail consistent with the contract commissioning requirements. All tasks associated with building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

These activities may include but are not limited to: air and water balancing, building commissioning -functional performance testing, controls testing, and performance verification testing. Include other systems testing, if required. Include additional commissioning requirements noted elsewhere in the Contract as required in the schedule and discuss during the SEKO meeting, noted in paragraph

SCHEDULING EXPECTATIONS KICKOFF MEETING (SEKO).

k. Contractor's pre-final inspection.

l. Correction of punch list from Contractor's pre-final inspection.

m. Government's pre-final inspection.

n. Correction of punch list from Government's pre-final inspection.

o. Final inspection.

3.3.6 Government Activities

Show in schedule, Government and other agency activities that could impact progress. These activities include, but are not limited to approvals, acceptance, design reviews, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.7 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

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

SECTION 01 32 01.00 10 Page 7

Field Activity Code Length Description

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.7.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.7.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.7.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.7.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.7.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

SECTION 01 32 01.00 10 Page 8 cost loaded. An activity can have only one BIDI Code.

3.3.7.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are design phase, 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.7.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 design, design submittal, design reviews, review conferences, permits, 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.7.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.8 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.8.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.8.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

SECTION 01 32 01.00 10 Page 9 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.8.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.8.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.8.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.9 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.10 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.11 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.

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

3.3.12 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

SECTION 01 32 01.00 10 Page 10 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.13 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.14 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.15 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.16 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.17 Retained Logic

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

3.3.18 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

SECTION 01 32 01.00 10 Page 11 referenced in paragraph COST LOADING of CLOSEOUT ACTIVITIES must have its budgeted cost increased by this amount.

3.3.19 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.20 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.20.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.20.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.21 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 hours) 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 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.

SECTION 01 32 01.00 10 Page 12

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…