Attachment_20_-_Reissued_Specs_.pdf

Dept. of Veterans Affairs - VA Livermore Re-Alignment and Closure Part B, Stockton CBOC

Section 01 12 19 Page 1

Construction Documents 03 JULY, 2018

SECTION 01 12 19

INTERFACE WITH OTHER WORK

08/17

PART 1 GENERAL

1.01 WORK BY OTHERS

The Government reserves the right to award other contracts for work at any time in the vicinity of the work required under this contract or to perform other new or ongoing work activities as follows:

A. Work by the Government Concurrent with Contractor Work

Government maintenance crews may perform normal maintenance or service call work in the vicinity of or adjacent to contract work.

The Government will limit interference with the Contractor's work to the maximum extent reasonable.

B. Work by Other Contractors

Work by other contractors may occur in the vicinity of or adjacent to the project site in concurrence with the performance of work under this contract.

C. Joint Use

Throughout the construction period, the Contractor should anticipate the need for Government personnel and/or Government contractors/venders to gain access to, and perform work, on the jobsite. This "Joint Use" by the Contractor and the Government is defined as a space or systems where minimal construction activities are shared with the using agency for the purpose of installing Government systems and/or equipment (i.e.:

telecommunications systems, research equipment, utility troughs, furniture, etc. - see contract drawings for equipment schedule of items installed by the Government or a vendor) in preparation for the outfitting and transitioning of staff and equipment for the new facility. See FAR Clause 52.236-11.

These areas, and their respective time windows for joint use, will be identified and coordinated with the Government contractor, through the USACE Construction Manager, a minimum of two (2) months prior to joint use. The Contractor will be responsible for integrating these specifically dated open-window milestones onto the updated project schedule and their status will be discussed at the regularly scheduled progress meetings with USACE. The integrated schedule will be the project schedule.

The Contractor shall develop a Coordination and Cooperation Work Plan based on the integrated schedule once the joint use needs are established. If necessary, and within reason as determined by the USACE Construction Manager, the Contractor shall provide the Government the means to reasonably secure such areas while work is being performed and after its completion. This may include the l2pmmmpn Cross-Out l2pmmmpn Callout Contracting Officer l2pmmmpn Cross-Out l2pmmmpn Callout the new schedule shall be called the Integrated Master Schedule (IMS) (See Section 01 32 01 PROJECT SCHEDULE). The status of the joint use spaces will be discussed at the regularly scheduled IMS meetings with USACE. See section 01 31 00 PROJECT MANAGEMENT, paragraph “Integrated Master Schedule Meetings” for specific requirements.

l2pmmmpn Text Box

AM-004 23 NOV 18

l2pmmmpn Cross-Out l2pmmmpn Callout Contracting Officer

Section 01 12 19 Page 2 early installation of doors, windows, removable core locks, temporary walls and doors, protection of finishes, etc. Pre and post inspections of joint use areas shall be conducted and recorded by the Contractor and agreed to by the USACE Construction Manager. The Contractor will not be held liable for damage caused by the Government.

Government contractors shall be supervised by Government personnel only, but shall adhere to the accepted safety plan/program requirements established by the Contractor. Access onto the jobsite (i.e., badging) by the Government contractors shall be the responsibility of the Contractor coordinated through the USACE Construction Manager.

1.02 GENERAL REQUIREMENTS

A. Coordination with Other Work

The Contractor shall make a special effort to fully cooperate with other contractors and Government employees engaged in other work on and adjacent to the work to be performed under this contract.

The Contractor shall coordinate the work herein and the concurrent use of haul roads, and utilities shall become a joint responsibility. Any damage resulting from the use of facilities of other contractors shall immediately be repaired to the satisfaction of or as directed by the Contracting Officer. If required and allowed, the Contractor shall construct and maintain a temporary detour around any road that is obstructed in the performance of work under this contract.

B. Interface of Work

Contractor will be advised of any other work activities at time of preconstruction conference and other times upon scheduling of activities. Upon notice of other work activities with contract interface or coordination requirements, the Contractor shall submit a Coordination and Cooperation Work Plan. The Contractor shall not commit or permit any act which will interfere with the performance of work by any other Contractor or Government personnel. The Contractor shall be liable for any costs incurred by the Government including those associated with settlement of disputes or claims by others due to, or arising from, the failure of the Contractor to comply with this provision.

1.03 COORDINATION MEETINGS

If interface with others is required, the Contractor shall meet with the Government along with any other Contractors working in the area to discuss and coordinate work activities. The Contractor shall present at the meeting, a 2-week Look Ahead Schedule (Refer to Section 01 32

01.00 10 PROJECT SCHEDULE for requirements) focusing on activities that may require coordination. Additional meetings shall be scheduled as required to discuss and coordinate work activities.

1.04 SUBMITTALS

l2pmmmpn Callout Contracting Officer l2pmmmpn Cross-Out l2pmmmpn Callout Contracting Officer l2pmmmpn Cross-Out l2pmmmpn Text Box

AM-004 23 NOV 18

l2pmmmpn

Government approval is required for submittals with a “G” designation; submittals not having a “G” designation are For Information Only. When used, a designation following the “G” designation identifies the office that will review the submittal for the Government.

Section 01 12 19 Page 3

The following shall be submitted in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-07 Certificates

Coordination and Cooperation Work Plan; G

This plan is required whenever work by others may occur in the vicinity of work under this contract that may cause an interface of work or require coordination of activities. Upon notification of such other work, the Contractor shall submit to the Contracting Officer for approval within ten (10) calendar days after receipt of the notice and thereafter revisions as required, a Coordination and Cooperation Work Plan describing the areas where interface with others may occur for all areas at the project site and staging area. This plan shall include, but not be limited to the following: description of other work activities requiring interface/ coordination, drawings showing areas of adjacent work activities, joint use of local access roads to the site(s); drawings showing proposed road detours; temporary utilities connections and use of temporary water and sewage disposal installations.

PART 2 PRODUCTS

Not Used.

PART 3 EXECUTION

Not Used.

-- End of Section --l2pmmmpn Cross-Out l2pmmmpn Callout Pre-Construction Submittals l2pmmmpn Callout (except Joint Use) l2pmmmpn Callout Joint Use Work Plan; G This plan shall specifically address joint use space requirements and interfaces required with Government personnel and/or Government contractor(s).

l2pmmmpn Text Box

AM-004 23 NOV 18

Section 01 31 00 Page 1

SECTION 01 31 00

PROJECT MANAGEMENT

08/17

PART 1 GENERAL

1.1 SUMMARY

The Contractor is responsible for management of the project and to coordinate activities of its own employees, subcontractors, suppliers and offsite fabricators. Contractor shall use computers, E-mail, and Internet resources for administrative work. Notify Contracting Officer of important meetings, schedule events and activities.

Furnish labor and materials and equipment required to plan and execute project management functions and coordination. Coordinate activities and manage resources to conform to contract, on time and within budget. The work includes all administrative provisions for coordinating construction operations for the New Community Based Out Patient Clinic and CUP.

1.2 ADMINISTRATIVE REQUIREMENTS

A. Government's Process

The Resident Engineer/Administrative Contracting Officer and his staff will use the web-based Construction Contract Administration (CCA) software system called Resident Management System (RMS) for tracking and responding to communications from the Contractor and for submitting requests, responses, and information to the Contractor. The Contractor shall use Resident Management System Contractor Mode (RMS CM). Refer to paragraph "REQUESTS FOR INFORMATION (RFI's)".

B. Contracting Officer

The Contracting Officer (CO) who signed this Contract is the primary Contracting Officer for the Contract. Nevertheless, any CO assigned to the Sacramento District and acting within his/her authority may take formal action on this Contract when a Contract action needs to be taken and the primary Contracting Officer is unavailable. All correspondence must be through the Contracting Officer or, upon notification, their authorized Representative

(COR).

1.3 LETTERS OF AUTHORITY AND KEY PERSONNEL

To authenticate actions required under terms of this Contract, furnish a letter of authority to the CO and Resident Engineer that indicates the names of individual or individuals who are authorized to perform the following functions on behalf of the company and hold key personnel positions:

A. Sign progress payment estimates.

B. Sign final payment estimate.

Section 01 31 00 Page 2

C. Accept Government-furnished property (if applicable).

D. Sign Contract modifications, supplemental agreements and consent of surety.

E. Monitor and report on the environmental protection plan, management plan, quality control plan, and safety plan.

F. Supervise the field activities.

G. Sign Release of Claims.

H. Sign Correspondence.

This letter of authority must bear the typewritten names and the handwritten signatures of each individual and be signed by the person whose signature appears on the final Contract.

1.4 SUBMITTALS

The following shall be submitted in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Letter of Authority and Key Personnel

Within 15 working days of notice to proceed, submit a Letter of Authority and a list of key personnel assignments, including superintendent and other personnel in attendance at Project site. Identify individuals and their duties and responsibilities; list addresses and telephone numbers, including home, office, and cellular telephone numbers and e-mail addresses. Provide names, addresses, and telephone numbers of individuals assigned as alternates in the absence of individuals assigned to Project.

Subcontract Summary

Post summary of list in project meeting room, in temporary field office, on RMS CM, and by each temporary telephone. Keep list current at all times and resubmit as required.

1.5 GENERAL COORDINATION PROCEDURES

Coordinate construction operations included in different Sections of the Specifications to ensure efficient and orderly installation of each part of the Work. Coordinate construction operations, included in different Sections which depend on each other for proper installation, connection, and operation.

A. Schedule construction operations in sequence required to obtain the best results where installation of one part of the Work depends on installation of other components, before or after its own installation.

l2pmmmpn Callout Government approval is required for submittals with a “G” designation; submittals not having “G” designation are for information only. When used, a designation following the “G” designation identifies the office that will review the submittals for the Government.

l2pmmmpn Callout

* IMS Schedule Updates. Required as specified prior to Integrated Master Schedule meetings.

* Data Management Plan, G

* SD-11 Closeout Submittals

* Red Zone Meeting Agenda l2pmmmpn

Section 01 31 00 Page 3

B. Coordinate installation of different components to ensure maximum performance and accessibility for required maintenance, service, and repair.

C. Make adequate provisions to accommodate items scheduled for later installation.

D. Subcontractor Coordination

The Contractor shall require each subcontractor to coordinate its construction operations with those of other subcontractors and entities to ensure efficient and orderly installation of each part of the Work. Each subcontractor shall coordinate its operations with operations included in different Sections that depend on each other for proper installation, connection, and operation. The Contractor shall:

1. Schedule construction operations in sequence required to obtain the best results where installation of one part of the Work depends on installation of other components, before or after its own installation.

2. Coordinate installation of different components with other subcontractors to ensure maximum performance and accessibility for required maintenance, service, and repair.

3. Make adequate provisions to accommodate items scheduled for later installation.

E. Distribution of Information

Prepare memoranda for distribution to each party involved, outlining special procedures required for coordination. Include such items as required notices, reports, and list of attendees at meetings.

1. Prepare similar memoranda for Government and separate

Contractors if coordination of their Work is required.

F. Administrative Procedures

Coordinate scheduling and timing of required administrative procedures with other construction activities and activities of other Contractors to avoid conflicts and to ensure orderly progress of the Work. Such administrative activities include, but are not limited to, the following:

1. Preparation of Contractor's construction schedule.

2. Preparation of the Schedule of Values.

3. Installation and removal of temporary facilities and controls.

4. Delivery and processing of submittals.

5. Progress meetings.

6. Pre-installation conferences.

7. Project closeout activities.

8. Startup and adjustment of systems.

Section 01 31 00 Page 4

G. Subcontract Summary

Prepare a written summary identifying individuals or firms proposed for each principal portion of the Work, including those who are to furnish materials or equipment fabricated to a special design. Include the following information in tabular form:

1. Name, address, and telephone number of entity performing subcontract or supplying products.

2. Number and title of related Specification Section(s) covered by subcontract. Drawing number and detail references, as appropriate, covered by subcontract.

H. Conservation

Coordinate construction activities to ensure that operations are carried out with consideration given to conservation of energy, water, and materials. Coordinate use of temporary utilities to minimize waste.

1.6 REQUESTS FOR INFORMATION (RFI'S)

Use the RFI generator and tracker in RMS CM. Refer to Section 01 45

00.15 10 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM).

I. Coordination Drawings Prepare coordination drawings in accordance with Section 01 43 43 l2pmmmpn Text Box

AM-004 23 NOV 18

l2pmmmpn Callout

PROJECT WEBSITE

A. General Provide, administer and use a Project Web site for purposes of hosting and managing project communication and documentation for the contract.

B. Secure Website A secure website shall be set up and maintained by the Contractor throughout the contract. All data stored on that site shall be accessible to COR and VAMC Poject Manager during the duration of the contract and as specified. This site will be used to house all documents as specified for the project. All submittals shall be maintained on the site for the duration of the contract. The site shall be established and COR and VAMC Project Manager provided access to the site no later than 30 days after notice to proceed has been issued.

Section 01 31 00 Page 5

C. On-Going Access to Data Contractor shall maintain COR access to project data for the duration of the project and for six months after contract completion. The secure site shall be available to COR personnel and VAMC Project Manager 24/7. Current firewall rules within COR specifically disallow push updates of software/data onto COR Servers. Contractor shall maintain access of COR personnel to data such that updates and information can be downloaded or accessed by electronic means initiated by the user (e.g. downloading information from an sFTP site, accessing data through a web based GIS, viewing and downloading data from a sharepoint site) unless Contractor requests and is granted a special exemption.

D. Data Updates New data, shall be available to the website no later than 48 hours after it is generated. All data which requires minimal processing, that is data which can be directly uploaded to the system without further processing or analysis shall be available to the website no later than 24 hours.

E. Data Management Plan Contractor shall submit a comprehensive “Data Management Plan” to COR for approval prior to start of construction activities. This plan shall be updated as required during the duration of the contract. The plan shall cover:

Project website shall include the following functions:

l2pmmmpn

Section 01 31 00 Page 6

1.7 PROJECT MEETINGS

A. General

Schedule and conduct meetings and conferences at Project site unless otherwise indicated.

1. Attendees: Inform participants and others involved, and individuals whose presence is required, of date and time of each meeting. Notify Government and Resident Engineer of scheduled meeting dates and times.

2. Agenda: Prepare the meeting agenda. Distribute the agenda to all invited attendees.

3. Minutes: Entity responsible for conducting meeting shall record significant discussions and agreements achieved.

Distribute the meeting minutes to everyone concerned, including Government and Resident Engineer, within three working days of the meeting.

4. Include each recorded project meeting/conference minutes in that day’s CQC Daily Report.

B. Preconstruction Conference

Schedule and conduct a preconstruction conference before starting construction, at a time convenient to Government and Resident l2pmmmpn Callout G. Training Session and User Manuals

l2pmmmpn

Section 01 31 00 Page 7

Engineer, but no later than 15 working days after notice to proceed.

1. Conduct the conference to review responsibilities and personnel assignments.

2. Attendees: Resident Engineer and Contracting Officer, Architect- Engineer and their consultants; Contractor and its l2pmmmpn

Space intentionally left blank

Section 01 31 00 Page 8 superintendent; major subcontractors; suppliers; and other concerned parties shall attend the conference. Participants at the conference shall be familiar with Project and authorized to conclude matters relating to the Work.

3. Agenda: Discuss items of significance that could affect progress, including the following:

a. Tentative construction schedule.

b. Phasing.

c. Critical work sequencing and long-lead items.

d. Designation of key personnel and their duties.

e. Lines of communications.

f. Procedures for processing field decisions and Change

Orders.

g. Procedures for RFIs.

h. Procedures for testing and inspecting.

i. Procedures for processing Applications for Payment.

j. Distribution of the Contract Documents.

k. Submittal procedures.

l. Preparation of record documents.

m. Use of the premises and existing building.

n. Work restrictions.

o. Working hours.

p. Government's occupancy requirements.

q. Responsibility for temporary facilities and controls.

r. Procedures for moisture and mold control.

s. Procedures for disruptions and shutdowns.

t. Construction waste management and recycling.

u. Parking availability.

v. Office, work, and storage areas.

w. Equipment deliveries and priorities.

x. First aid.

y. Security.

z. Progress cleaning.

4. Minutes: Entity responsible for conducting meeting shall record and distribute meeting minutes.

C. Pre-installation Conferences

Conduct a pre-installation conference at Project site before each construction activity that requires coordination with other construction.

1. Record significant conference discussions, agreements, and disagreements, including required corrective measures and actions.

2. Reporting: Distribute minutes of the meeting to each party present and to other parties requiring information.

3. Do not proceed with installation if the conference cannot be successfully concluded. Initiate whatever actions are necessary to resolve impediments to performance of the Work and reconvene the conference at earliest feasible date.

Section 01 31 00 Page 9

D. Project Closeout Conference

Schedule and conduct a project closeout conference, at a time convenient to Government and Resident Engineer, but no later than 90 days prior to the scheduled date of Substantial Completion.

1. Conduct the conference to review requirements and responsibilities related to Project closeout.

2. Attendees: Authorized representatives of Government, Resident Engineer, Architect-Engineer and their consultants; CONTRACTOR and its superintendent; major subcontractors; suppliers; and other concerned parties shall attend the meeting. Participants at the meeting shall be familiar with Project and authorized to conclude matters relating to the Work.

3. Agenda: Discuss items of significance that could affect or delay Project closeout, including the following:

a. Preparation of record documents.

b. Procedures required prior to inspection for Substantial

Completion and for final inspection for acceptance.

c. Submittal of written warranties.

d. Requirements for preparing operations and maintenance data.

e. Requirements for delivery of material samples, attic stock, and spare parts.

f. Requirements for demonstration and training.

g. Preparation of CONTRACTOR's punch list.

h. Procedures for processing Applications for Payment at

Substantial Completion and for final payment.

i. Submittal procedures.

j. Coordination of separate contracts.

k. Government's partial occupancy requirements.

l. Installation of Government's furniture, fixtures, and equipment.

m. Responsibility for removing temporary facilities and controls.

4. Minutes: Entity conducting meeting shall record and distribute meeting minutes.

E. Progress Meetings

Conduct progress meetings at agreed upon intervals.

1. Coordinate dates of meetings with preparation of payment requests.

2. Attendees: In addition to representatives of Government and Resident Engineer, each Contractor, subcontractor, supplier, and other entity concerned with current progress or involved in planning, coordination, or performance of future activities shall be represented at these meetings. All participants at l2pmmmpn Callout Red Zone l2pmmmpn Callout and prior to final acceptance inspection of the last or only contract schedule item of work. Discuss the close-out process, schedule the events and review responsibilities for actions necessary to produce a timely physical, as well as fiscal, project close-out. The Red Zone meeting derives its name from the football term used to describe the team effort to move the ball the last 20 yards into the end zone. The close-out of a construction project sometimes can be equally as hard and most definitely requires the whole team's efforts. The ACO will chair the meeting.

l2pmmmpn Callout

1. Prepare a comprehensive proposed Red Zone Meeting agenda and checklist and submit to COR 14 Calendar days prior to date of Red Zone Meeting.

l2pmmmpn

Section 01 31 00 Page the meeting shall be familiar with Project and authorized to conclude matters relating to the Work.

3. Agenda: Review and correct or approve minutes of previous progress meeting. Review other items of significance that could affect progress. Include topics for discussion as appropriate to status of Project.

a. Contractor's Construction Schedule: Review progress since the last meeting. Determine whether each activity is on time, ahead of schedule, or behind schedule, in relation to l2pmmmpn

Space intentionally left blank

Contractor's construction schedule. Determine how construction behind schedule will be expedited; secure commitments from parties involved to do so. Discuss whether schedule revisions are required to ensure that current and subsequent activities will be completed within the Contract Time.

b. Review schedule for next period.

c. Review present and future needs of each entity present, including the following:

1) Interface requirements.

2) Sequence of operations.

3) Resolution of BIM component conflicts.

4) Status of submittals.

5) Deliveries.

6) Off-site fabrication.

7) Access.

8) Site utilization.

9) Temporary facilities and controls.

10) Progress cleaning.

11) Quality and work standards.

12) Status of correction of deficient items.

13) Field observations.

14) Status of RFI's.

15) Status of proposal requests.

16) Pending changes.

17) Status of Change Orders.

18) Pending claims and disputes.

19) Documentation of information for payment requests.

4. Minutes. Entity responsible for conducting the meeting shall record and distribute the meeting minutes to each party present and to parties requiring information.

a. Schedule Updating:

1) Revise Contractor's construction schedule after each progress meeting where revisions to the schedule have been made or recognized.

2) Issue revised schedule concurrently with the report of each meeting.

F. Coordination Meetings

Conduct Project coordination meetings at agreed upon intervals.

Project coordination meetings are in addition to specific meetings held for other purposes, such as progress meetings and pre-installation conferences.

1. Attendees: In addition to representatives of Government and

Resident Engineer, each Contractor, subcontractor, supplier, and other entity concerned with current progress or involved in planning, coordination, or performance of future activities shall be represented at these meetings. All participants at the meetings shall be familiar with Project and authorized to conclude matters relating to the Work.

2. Agenda: Review and correct or approve minutes of the previous coordination meeting. Review other items of significance that could affect progress. Include topics for discussion as appropriate to status of Project.

a. Combined Contractor's Construction Schedule:

1) Review progress since the last coordination meeting.

2) Determine whether each contract is on time, ahead of schedule, or behind schedule, in relation to combined Contractor's construction schedule.

3) Determine how construction behind schedule will be expedited; secure commitments from parties involved to do so.

4) Discuss whether schedule revisions are required to ensure that current and subsequent activities will be completed within the Contract Time.

b. Schedule Updating: Revise combined Contractor's construction schedule after each coordination meeting where revisions to the schedule have been made or recognized.

Issue revised schedule concurrently with report of each meeting.

c. Review present and future needs of each Contractor present, including the following:

1) Interface requirements.

2) Sequence of operations.

3) Resolution of BIM component conflicts.

4) Status of submittals.

5) Construction waste management and recycling.

6) Sequence of finish installation and indoor air quality procedures.

7) Deliveries.

8) Off-site fabrication.

9) Access.

10) Site utilization.

11) Temporary facilities and controls.

12) Work hours.

13) Hazards and risks.

14) Progress cleaning.

15) Quality and work standards.

16) Status of correction of deficient items.

17) Field observations.

18) Requests for interpretations (RFI's).

19) Status of Proposal Requests (PR's).

20) Pending changes.

21) Status of Change Orders.

22) Pending claims and disputes.

23) Documentation of information for payment requests.

24) Participation in Coordination meetings, testing and training activities identified in the Commissioning Plan for the project, to be provided by the Commissioning Authority.

3. Reporting: Record meeting results and distribute copies to everyone in attendance and to others affected by decisions or actions resulting from each meeting.

G. Integrated Master Schedule Meetings The contractor shall integrate the Government's Major Milestones into its Project Schedule, and shall attend monthly IMS Meetings, providing critical status reports, to the Government, for discussion.

Conduct Integrated Master Schedule (IMS) Meetings, which shall be separate from and in addition to the other described meetings.

l2pmmmpn

PART 2 PRODUCTS

PART 3 EXECUTION

Section 01 32 01.00 10 Page 1 Construction Documents 03 JULY, 2018

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.01 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (1995) Administration -- Progress, Schedules, and Network Analysis Systems

1.02 SUBMITTALS

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.03 PROJECT SCHEDULER QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The authorized representative must have a minimum of 2-years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. Representative must have a comprehensive knowledge of CPM scheduling principles and application.

l2pmmmpn Callout ECB 2005-10 (2005) Scheduling Requirements for Testing of Mechanical Systems in Construction Administration l2pmmmpn Callout G l2pmmmpn

AM-0004 23 NOV 18

Section 01 32 01.00 10 Page 2 Construction Documents 03 JULY, 2018

PART 2 PRODUCTS

2.01 SOFTWARE

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

A. Government Default Software

The Government intends to use Primavera P6.

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

1. Primavera

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.

2. 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.01 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development.

Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule.

Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules. Prepare each Project Schedule using the Precedence Diagram Method (PDM).

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

l2pmmmpn Callout

3.1 Integrated Master Schedule (IMS)

The Project Schedule shall provide for an Integrated Master Schedule (IMS) to include the contract milestones, accomplishments, and discrete tasks/activities (including planning packages where applicable) and activities requiring “Joint Use” spaces from contract award to the completion of the contract. Requirements for “Joint Use” space is described in Section 01 12 19 INTERFACE WITH OTHER WORK.

l2pmmmpn

Section 01 32 01.00 10 Page 3 Construction Documents 03 JULY, 2018

The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN.

A. Activity Cost Loading

Activity cost loading must be reasonable and without front-end loading. Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.

B. 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.03 PROJECT SCHEDULE DETAILED REQUIREMENTS

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

B. Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods. Less than 2 percent of all non-procurement activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

C. Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies.

Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

Section 01 32 01.00 10 Page 4 Construction Documents 03 JULY, 2018

D. Mandatory Tasks

Include the following activities/tasks in the initial project schedule and all updates.

1. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each).

2. Submission, review and acceptance of features require design completion

3. Submission of mechanical/electrical/information systems layout drawings.

4. Long procurement activities

5. Submission and approval of O & M manuals.

6. Submission and approval of as-built drawings.

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

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

9. Submission of TAB specialist design review report.

10. Submission and approval of fire protection specialist.

E. Submission and approval of Building Commissioning Plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with the contract commissioning requirements. All tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

l. Air and water balancing.

2. Building commissioning - Functional Performance Testing.

3. Controls testing plan submission.

4. Controls testing.

5. Performance Verification testing.

6. Other systems testing, if required.

7. Contractor's pre-final inspection.

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

9. Government's pre-final inspection.

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

11. Final inspection.

F. Government Activities

Show Government and other agency activities that could impact progress. These activities include, but are not limited to:

approvals, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

G. Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site: http://rms.usace.army.mil.

l2pmmmpn Text Box

AM-0004 23 NOV 18

l2pmmmpn

Red Zone Meeting

Section 01 32 01.00 10 Page 5 Construction Documents 03 JULY, 2018

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the FEATURE OF WORK field requirements.

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.

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

Section 01 32 01.00 10 Page 6 Construction Documents 03 JULY, 2018

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.

Not all activities are required to be Work Area coded. A lack of Work Area coding indicates the activity is not resource or space constrained.

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.

5. Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code.

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.

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.

Section 01 32 01.00 10 Page 7 Construction Documents 03 JULY, 2018

8. Feature of Work Coding (FOW)

Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan.

Definable Feature of Work is defined in Section 01 45 00.00 10 QUALITY CONTROL. An activity can have only one Feature of Work Code.

H. 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 effect network logic are prohibited. No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.

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.

2. End Project Finish Milestone and Constraint

The last activity in the schedule must be a finish milestone titled "End Project."

Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path.

The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

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

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

Section 01 32 01.00 10 Page 8 Construction Documents 03 JULY, 2018

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

I. Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop sSeasonal Calendar(s) and assign to seasonally affected activities as applicable.

If an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated days provided in the contract clause TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends.

J. Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Acknowledged" may have no predecessor logic, and the last activity -"End Project" may have no successor logic.

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

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

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