Attachment Q - Updated Specs.pdf

Building 195 Demolition 1606626 Norfolk Naval Shipyard, Portsmouth, VA

SECTION 01 20 00

PRICE AND PAYMENT PROCEDURES

11/20, CHG 3: 02/23

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)

EP 1110-1-8 (2021) Engineering and Design -- Construction Equipment Ownership and Operating Expense Schedule

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. Submit the following in accordance with Section 01 33 00.05 20 CONSTRUCTION SUBMITTAL PROCEDURES and Section

01 33 10.05 20 DESIGN SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Earned Value Report ; G

1.3 EARNED VALUE REPORT

1.3.1 Data Required

This Contract requires the use of a cost-loaded Network Analysis Schedule (NAS). Schedule of Prices must not be used with cost-loaded Network Analysis Schedule (NAS). Use Earned Value Report derived from cost-loaded NAS. Within 1545 calendar days of notice of award, prepare and deliver to the Contracting Officer a Earned Value Report (construction Contract) as directed by the Contracting Officer. Provide a detailed breakdown of the Contract price, giving quantities for each of the various kinds of work, unit prices and extended prices. Contractor overhead and profit including salaries for field office personnel, if applicable, must be proportionately spread over all pay items and not included as individual pay items.

1.3.2 Payment Schedule Instructions

Payments will not be made until the Earned Value Report from the cost-loaded NAS has been submitted to and accepted by the Contracting Officer. For design phase progress payment(s), Earned Value Report from the Cost Loaded CPM must include detailed design activities and general (summarized) approach for the construction phase(s) of the project. The Earned Value Report must be fully developed with detailed construction line items as design progresses. The complete design and construction Earned Value Report must be submitted and accepted prior to starting construction work.

SECTION 01 20 00 Page 1

For Fast-Tracked or Critical Path Submittals of construction projects, the Earned Value Report must include detailed design and construction line items for each fast-tracked/ critical path phase(s), submitted to and accepted by the Contracting Officer during the Post Award Kickoff Meetings and confirmed prior to starting construction work in that phase.

Additionally, the Earned Value Report must be separated as follows:

a. Primary Facilities Cost Breakdown:

Defined as work on the primary facilities out to the 5 foot line.

Work out to the 5 foot line includes construction encompassed within a theoretical line 5 foot from the face of exterior walls and includes attendant construction, such as pad mounted HVAC cooling equipment, cooling towers, and transformers placed beyond the 5 foot line.

b. Supporting Facilities Cost Breakdown:

Defined as site work, including incidental work, outside the 5 foot line.

1.4 CONTRACT MODIFICATIONS

In conjunction with the Contract Clause DFARS 252.236-7000 Modification Proposals-Price Breakdown, and where actual ownership and operating costs of construction equipment cannot be determined from Contractor accounting records, base equipment use rates upon the applicable provisions of the

EP 1110-1-8 .

1.5 CONTRACTOR'S INVOICE AND CONTRACT PERFORMANCE STATEMENT

1.5.1 Content of Invoice

Requests for payment will be processed in accordance with the Contract Clause FAR 52.232-27 Prompt Payment for Construction Contracts and FAR 52.232-5 Payments Under Fixed-Price Construction Contracts. Invoices not completed in accordance with contract requirements will be returned to the Contractor for correction of the deficiencies. The requests for payment shall include the documents listed below.

a. The Contractor's invoice, on NAVFAC Form 7300/30 furnished by the Government, showing in summary form, the basis for arriving at the amount of the invoice. Form 7300/30 must include certification by Quality Control (QC) Manager as required by the Contract.

b. The Earned Value Report from the cost-loaded NAS.

c. Contractor's Monthly Estimate for Voucher and Contractors Certification (NAVFAC Form 4330) with Subcontractor and supplier payment certification. Other documents, including but not limited to, that need to be received prior to processing payment include the following submittals as required. These items are still required monthly even when a pay voucher is not submitted.

d. Monthly Work-hour report.

e. Updated Construction Progress Schedule and tabular reports required by the contract.

SECTION 01 20 00 Page 2

f. Contractor Safety Self Evaluation Checklist.

g. Updated submittal register.

h. Solid Waste Disposal Report.

i. Certified payrolls.

j. Updated testing logs.

k. Other supporting documents as requested.

1.6 PAYMENTS TO THE CONTRACTOR

Payments will be made on submission of itemized requests by the Contractor which comply with the requirements of this section, and will be subject to reduction for overpayments or increase for underpayments made on previous payments to the Contractor.

1.6.1 Obligation of Government Payments

The obligation of the Government to make payments required under the provisions of this Contract will, at the discretion of the Contracting Officer, be subject to reductions and suspensions permitted under the FAR and agency regulations including the following in accordance with FAR

32.103 Progress Payments Under Construction Contracts:

a. Reasonable deductions due to defects in material or workmanship;

b. Claims which the Government may have against the Contractor under or in connection with this Contract;

c. Unless otherwise adjusted, repayment to the Government upon demand for overpayments made to the Contractor; and

d. Failure to maintain accurate "as-built" or record drawings in accordance with FAR 52.236.21.

1.6.2 Payment for Onsite and Offsite Materials

Progress payments may be made to the Contractor for materials delivered on the site, for materials stored off construction sites, or materials that are in transit to the construction sites under the following conditions:

a. FAR 52.232-5(b) Payments Under Fixed Price Construction Contracts.

b. Materials delivered on the site but not installed, including completed preparatory work, and off-site materials to be considered for progress payment must be major high cost, long lead, special order, or specialty items, not susceptible to deterioration or physical damage in storage or in transit to the construction site. Examples of materials acceptable for payment consideration include, but are not limited to, structural steel, non-magnetic steel, non-magnetic aggregate, equipment, machinery, large pipe and fittings, precast/prestressed concrete products, plastic lumber (e.g., fender piles/curbs), and high-voltage electrical cable. Materials not acceptable for payment include consumable materials such as nails, fasteners, conduits, gypsum board, glass, insulation, and wall coverings.

SECTION 01 20 00 Page 3

c. Materials to be considered for progress payment prior to installation must be specifically and separately identified in the Contractor's estimates of work submitted for the Contracting Officer's approval in accordance with Earned Value Report requirement of this Contract.

Requests for progress payment consideration for such items must be supported by documents establishing their value and that the title requirements of the clause at FAR 52.232-5 Payments Under Fixed-Price Construction Contracts have been met.

d. Materials are adequately insured and protected from theft and exposure.

e. Provide a written consent from the surety company with each payment request for offsite materials.

f. Materials to be considered for progress payments prior to installation must be stored either in Hawaii, Guam, Puerto Rico, or the Continental United States. Other locations are subject to written approval by the Contracting Officer.

g. Materials in transit to the job site or storage site are not acceptable for payment.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

-- End of Section --

SECTION 01 20 00 Page 4

SECTION 01 30 00.00 22

ADMINISTRATIVE REQUIREMENTS

11/20, CHG 2: 05/22

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00.05 20 CONSTRUCTION SUBMITTAL PROCEDURES and Section 01 33 10.05 20 DESIGN SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

View Location Map

Progress and Completion Pictures

Qualifications of Superintendent; G

1.2 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.3 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.4 MINIMUM INSURANCE REQUIREMENTS

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

1.4.1 Additional Insurance Requirements

a. Before commencing work under this contract, the Contractor shall certify to the Contracting Officer in writing that the required insurance has been obtained. The policies evidencing required insurance shall contain an endorsement to the effect that any

SECTION 01 30 00.00 22 Page 1 cancellation or any material change adversely affecting the Government's interest shall not be effective (1) for such period as the laws of the State in which this contract is to be performed prescribe or (2) until 30 days after the insurer or the Contractor gives written notice to the Contracting Officer, whichever period is longer.

b. The Contractor shall insert the substance of this clause, including this paragraph b., in subcontracts under this contract that require work on a Government installation and shall make copies available to the Contracting Officer upon request.

1.5 SUPERVISION

1.5.1 Superintendent Qualifications

The Superintendent for this contract is to have a minimum of seven years experience as a Superintendent, QC Manager, Project Manager or Construction Manager on similar size (dollar wise) and type construction contracts which included the major trades that are part of this contract.

He is to be capable of reading, writing, and conversing in the English language on the job site during working hours. Provide a submittal on superintendent qualifications as indicated in the paragraph entitled, "Submittals." The superintendent shall be subject to an interview by the construction office.

In addition to the above experience requirements, the Project Manager and on-site Project Superintendent shall complete the course entitled "Construction Quality Management for Contractors" prior to the start of construction.

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

SECTION 01 30 00.00 22 Page 2

1.6 PRECONSTRUCTION MEETING

Immediately after award, prior to commencing any work at the site, coordinate with the Contracting Officer a time and place to meet for the Preconstruction Meeting. The meeting must take place within 35 calendar days after award of the contract, but prior to commencement of any work at the site. The purpose of this meeting is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to: daily reporting, invoicing, value engineering, safety, base-access, outage requests, hot work permits, schedule requirements, quality control, schedule of prices or earned value report, shop drawings, submittals, cybersecurity, prosecution of the work, government acceptance, final inspections and contract close-out. Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.

1.6.1 Attendees

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

1.7 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 NRZ Meetings beginning at approximately 75 percent of project completion.

Include the following in the facility Turnover effort:

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

SECTION 01 30 00.00 22 Page 3

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.

1.8 PARTNERING

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, NAVFAC, PWD, FEAD/ROICC, Contractor, key subcontractors and the Designer of Record are required to participate in the Partnering process.

1.8.1 Facilitated (Formal) Partnering

a. Within 35120 calendar days after award and prior to the start of work, host a Formal Partnering session with key personnel from the project team including both Contractor and Government personnel. All costs associated with the Partnering session including the third-party independent Facilitator Consultant, meeting room and other incidental items are the responsibility of the Contractor.

b. Before the Facilitated (Formal) Partnering session, coordinate with the Facilitator all requirements for incidental items (such as audio-visual equipment, easels, flipchart paper, colored markers, note pads, pens/pencils, colored flash cards) and have these items available at the Partnering session. Provide copies of any documents required for distribution to all attendees. Participants will bear their own costs for meals, lodging and transportation associated with Partnering .

c. The Initial Partnering Session must be a duration of one day and be held at a location off base as agreed to by the Contracting Officer.

Partnering session may take place concurrently with the Pre-Construction Meeting.

d. Facilitator must be experienced in conducting corporate Partnering sessions and must be a third-party independent facilitating consultant

- not an employee of the Contractor. The Facilitator is responsible for leading all aspects of the Partnering session necessary to achieve the Partnering goal.

e. An outcome of the Partnering session must be an escalation matrix agreed upon by both the Government and Contractor, which identifies key Government and Contractor decision makers by name and anticipated decision durations.

f. Host follow-on Partnering Sessions at three- to six-month intervals or more frequently if needed and lasting generally a half day or less.

Attendees need only be those required to resolve current issues. The

SECTION 01 30 00.00 22 Page 4 same Facilitator used in the Initial Partnering session must lead the follow-on sessions unless an alternative is permitted by the Contractor Officer. All costs associated with follow-on Partnering sessions are the responsibility of the Contractor.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 30 00.00 22 Page 5

SECTION 01 32 17.00 20

COST-LOADED NETWORK ANALYSIS SCHEDULES (NAS)

11/23

PART 1 GENERAL

1.1 DEFINITIONS

The cost-loaded Network Analysis Schedule (NAS) is a tool to manage the project, both for Contractor and Government activities. The NAS is also used to report progress, evaluate time extensions, and provide the basis for progress payments.

For consistency, when scheduling software terminology is used in this section, the terms in Primavera's scheduling programs are used.

1.2 SCHEDULE REQUIREMENTS PRIOR TO THE START OF WORK

1.2.1 Preliminary Scheduling Meeting

Before preparation of the Project Baseline Schedule, and prior to the start of work, and within 35 days of award, meet with the Contracting Officer to discuss the proposed schedule and the requirements of this section. Propose projected data dates for monthly update schedules for the project and incorporate each monthly update submittal into submittal register. Discuss required forms, terminology, and submittal requirements of this section and other requirements related to schedule management for this contract. Use the NAVFAC-provided Preliminary Scheduling Meeting Guideline in the completion of the intended mutual understanding.

1.2.2 Project Baseline Schedule

Submit the Baseline NAS within 45 calendar days after contract award.

Data date must be set to contract award date and no progress recorded for any activity. Only bonds and the required Preliminary Scheduling Meeting may be recorded as complete prior to acceptance of the Baseline NAS. The acceptance of a Baseline NAS is a condition precedent to:

a. The Contractor starting demolition work or construction stage(s) of the contract.

b. Processing Contractor's invoices(s) for any items other than bonds.

c. Review of any schedule updates. The contractor is still required to submit monthly network analysis updates. Without an accepted baseline the Government may return schedule update as received for record.

Submittal of the Baseline NAS is the Contractor's certification that the submitted schedule meets the requirements of the Contract Documents and represents the Contractor's plan on how the work will be accomplished.

Provide all items listed in paragraph REQUIRED TABULAR REPORTS AND NATIVE P6 XER FILES with baseline NAS submittal.

SECTION 01 32 17.00 20 Page 1

1.2.3 Project Baseline Schedule

1.2.3.1 Baseline NAS

Submit the Baseline NAS at the Post-Award Kickoff (PAK) Meeting or within 30 calendar days after contract award whichever occurs first. The Baseline schedule must include detailed design activities and a general approach to construction, including summary activities for required phasing and definable areas. Summary Construction activities must not exceed duration of 60 calendar days, unless approved otherwise by Contracting Officer. Data date must be set to contract award date and no progress recorded for any activity.

Only bonds and the required Preliminary Scheduling Meeting may be recorded as complete prior to acceptance of the Baseline NAS. The acceptance of a Baseline NAS is a condition precedent to:

a. The Contractor submitting the first design submittal.

b. Processing Contractor's invoices(s)other than that for the bonds.

1.2.3.2 Post-Award Kickoff (PAK) Meeting and Baseline NAS

Present the Draft Baseline NAS at the PAK Meeting. Be prepared to discuss the schedule logic emphasizing how the schedule satisfies the design package requirements and incorporates the required government review periods for each design submittal.

1.2.3.3 Construction Baseline

Submit the detailed Construction Baseline NAS prior to the pre-final design submittal. The pre-final design submittal will not be reviewed until a Construction Baseline NAS is submitted.

The acceptance of the Construction Baseline NAS is a condition precedent to:

a. The contractor starting demolition work or construction stage(s) of the contract.

b. Processing Contractor's invoices for demolition or construction activities.

c. Review of any construction phase schedule updates.

Submittal of the Construction Baseline NAS must be the Contractor's certification that the submitted schedule meets the requirements of the Contract Documents, and represents the Contractor's plan on how the work will be accomplished. Provide all items listed in paragraph REQUIRED TABULAR REPORTS AND NATIVE P6 XER FILES with baseline NAS submittal.

1.3 WEEKLY LOOK AHEAD SCHEDULE

1.3.1 Weekly CQC Coordination and Production Meeting

Submit the first look ahead schedule 30 days after contract award and continue to submit weekly until contract completion.

Transmit the Weekly Look Ahead Schedule Submittal to the Contracting

SECTION 01 32 17.00 20 Page 2

Officer on the first day of the current week that the look ahead schedule covers and at least one working day prior to Quality Control meetings or as agreed to by Contracting Officer. Contractor is required to provide all attendees at meetings that require discussion of the schedule.

1.3.2 Weekly Look Ahead Schedule Requirements

Prepare and issue a Three-Week Look Ahead schedule to provide a more detailed day-to-day plan of upcoming work identified on the Project Network Analysis Schedule. Requirements include:

a. For each Look Ahead schedule activity, identify parent NAS activity number(s). The parent NAS activity is the activity in the NAS that would incorporate the Look Ahead schedule activity requirement and scope of work.

b. Update schedule each week to show the planned work for the current and following two-week period. Also include previous week, as-built work, showing actual start and finish dates.

c. Include upcoming outages, closures, preparatory meetings, and initial meetings, testing and inspections.

d. Clearly identify longest path activities on the Weekly Look Ahead Schedule. Include a key or legend that distinguishes longest path activities. Include all Longest Path activity NAS start/finish dates exceeded or occurring during this period.

e. Identify responsibility for each activity.

f. The detail work plans are to be bar chart type schedules, derived from but maintained separately from the Project NAS on an electronic spreadsheet program and printed on 11 by 17 inch sheets as directed by the Contracting Officer.

g. Activities must not exceed 5 working days in duration and have sufficient level of detail to assign crews, tools and equipment required to complete the work.

h. Lookahead activities are not limited to only onsite work. Include but not limited to submittal, offsite fabrication, and procurement activities if needed to ensure longest path is maintained. Include design activities and coordination when part of scope.

i. Upload Lookahead to eCMS as a submittal by the date and time required by contracting officer.

1.4 MONTHLY NETWORK ANALYSIS

Submittal of Monthly NAS is the Contractor's certification that the submitted schedule meets the requirements of the Contract Documents and represents the Contractor's plan on how the work will be accomplished.

Provide all items listed in paragraph REQUIRED TABULAR REPORTS AND NATIVE P6 XER FILES with the monthly NAS submittal.

1.4.1 Monthly Network Analysis Updates

a. Regardless of whether an invoice is being submitted monthly, or no progress in the schedule occurred, an updated schedule (or with new

SECTION 01 32 17.00 20 Page 3 data date) must be submitted monthly to the Government. The Monthly NAS update must be submitted within 10 calendar days of the data date.

b. Regardless of whether a baseline or other schedule is submitted and accepted, an updated schedule must be submitted monthly to the Government. Monthly updates submitted before the baseline being accepted will be considered as (interim and for information only) submittal.

c. Provide all items listed in paragraph REQUIRED TABULAR REPORTS AND NATIVE P6 XER FILES, with each monthly NAS update submittal.

d. Meet with Government representative(s) at monthly intervals to review and agree on the information presented in the updated project schedule. The submission of an accepted, updated schedule to the Government is a condition precedent to the processing of the Contractor's invoice.

e. Activity progress must incorporate as-built events as they occurred and correspond to records including but not limited to submittals and daily production and quality control reports.

f. Software Settings: Handle schedule calculations and Out-of-Sequence progress (if applicable) through Retained Logic, not Progress Override. Show all activity durations and float values in days. Show activity progress using Remaining Duration. Set default activity type to "Task Dependent".

g. Update schedule must reflect current Contract Completion Date and contract value in accordance with all conformed contract modifications issued prior to data date of NAS update.

1.4.2 As-Built Schedule

As a condition precedent to the release of retention and making final payment, submit an "As-Built Schedule," as the last schedule update showing all activities at 100 percent completion. This schedule must reflect the exact manner in which the project was actually constructed.

1.5 CORRESPONDENCE AND TEST REPORTS

Reference Schedule activity IDs that are being addressed in each correspondence (e.g., letters, Requests for Information (RFIs), e-mails, meeting minute items, Production and QC Daily Reports, material delivery tickets, photographs) and test report (e.g., concrete, soil compaction, weld, pressure).

1.6 ADDITIONAL SCHEDULING REQUIREMENTS

Other specification sections may include additional scheduling requirements, including systems to be inspected, tested and commissioned, and submittal procedures. Those schedule requirements must be incorporated into the NAS schedule.

1.7 SUBMITTALS

Government approval/acceptance is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in

SECTION 01 32 17.00 20 Page 4 accordance with Section 01 33 00.05 20 CONSTRUCTION SUBMITTAL PROCEDURES and Section 01 33 10.05 20 DESIGN SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Baseline NAS ; G

Construction Baseline NAS ; G

Designated Project Scheduler ; G

SD-07 Certificates

Weekly Look Ahead Schedule

Monthly Network Analysis Updates ; G

SD-11 Closeout Submittals

As-Built Schedule ; G

1.8 SOFTWARE

Prepare and maintain project schedules using Primavera P6 software in a version compatible with Government's current version. Importing data into P6 using data conversion techniques or third party software is cause for rejection of the submitted schedule. Schedules with Performing Organizational Breakdown Structure (POBS) data is cause for rejection.

1.9 DESIGNATED PROJECT SCHEDULER

Within 3025 calendar days of contract award, submit to the Contracting Officer for approval an individual who will serve as the Designated Project Scheduler. Include a copy of the candidate's resume with qualifications. The Contracting Officer may remove the Designated Project Scheduler, and require replacement, if the scheduler does not effectively fulfill their duties in accordance with the contract requirements.

Payment request will not be processed without an approved Designated Project Scheduler.

1.9.1 Qualifications

The Designated Project Scheduler must have prepared and maintained at least three previous construction schedules, of similar size and complexity to this contract, using Primavera P6.

1.9.2 Duties

Duties of the Designated Project Scheduler include to be actively involved and be responsible for the following::

a. Prepare Baseline NAS.

b. Prepare monthly schedule updates.

c. Prepare tabular reports.

d. Prepare Time Impact Analysis (TIA) as necessary.

SECTION 01 32 17.00 20 Page 5

e. Provide certification that NAS and TIA submittals conform to the contract requirements.

1.10 NETWORK SYSTEM FORMAT

Prepare the schedule in accordance with the following Primavera P6 settings and parameters. Deviation from these settings and parameters, without prior consent of the Contracting Officer, is cause for rejection of schedule submission.

1.10.1 Schedule Activity Properties and Level of Detail

1.10.1.1 Activity Identification and Organization

a. Identify design and construction activities planned for the project and other activities that could impact project completion if delayed in the NAS.

b. Each activity must have a unique name.

c. Identify administrative type activity/milestones, including all pre-construction submittal and permit requirements prior to demolition or construction stage.

d. Include times for procurement, Contractor quality control and construction, acceptance testing and training in the schedule.

e. Include the Government approval time required for the submittals that require Government Approval prior to construction, as indicated in Section 01 33 00.05 20 CONSTRUCTION SUBMITTAL PROCEDURES .

f. Create separate activities for each Phase, Area, Floor Level and Location the activity is occurring.

g. Do not use construction category activity to represent non-work type reference (e.g., Serial Letter, Request for Information) in NAS.

Place Non-work reference within the P6 activity details notebook.

Activity categories included in the schedule are specified below.

1.10.1.2 Activity Logic

a. With the exception of the Contract Award and Contract Completion Date (CCD) milestone activities, activity must not be open-ended; each activity must have at least one predecessor and at least one successor.

b. Activities must not have open start or open finish (dangling) logic.

c. Do not use lead or lag logic without Contracting Officer prior approval.

d. Minimize redundant logic ties.

e. Once an activity exists on the schedule it must not be deleted or renamed to change the scope of the activity and must not be removed from the schedule logic without approval from the Contracting Officer.

(1) While an activity cannot be deleted, where said activity is no longer applicable to the schedule, but must remain within the

SECTION 01 32 17.00 20 Page 6 logic stream for historical record, change the activity original and remaining duration to zero and clearly label "(NO LONGER REQUIRED)" after the activity name. Actual finish date for activity that falls behind the data date. Redistribute accordingly any remaining budget associated with that activity, to other remaining appropriate activity.

(2) Document any such change in the activities' "Notebook," including a date and explanation for the change.

(3) The ID number for a "NO LONGER REQUIRED" activity must not be re-used for another activity.

1.10.1.3 Longest Path Activity Baseline Limitation

For P6 settings, critical activities are defined as being on the Longest Path. Longest Path (Critical) Activities must not make up more than 30 percent of all activity within the Construction Baseline Schedule.

1.10.1.4 Assigned Calendars

All NAS activity must be assigned calendars that reflect required and anticipated non-work days.

1.10.1.5 Activity Categories

1.10.1.5.1 Design Activities

Design activities must include design decision points and design submittal packages, including critical path submittals for Fast Tracked Phases.

Review times for design development packages must be included in the schedule. Refer to Section 01 33 10.05 20 DESIGN SUBMITTAL PROCEDURES, for specific requirements.

1.10.1.5.2 Pre-construction Activities

Examples of pre-construction activities include, but are not limited to, bond approval, permits, pre-construction submittals and approvals.

Include pre-construction activities that are required to be completed prior to the Contractor starting the demolition or construction stage of work.

1.10.1.5.3 Procurement Activities

Examples of procurement activities include, but are not limited to:

Material/equipment submittal preparation, submittal and approval of material/equipment; material/equipment fabrication and delivery, and material/equipment on-site. As a minimum, separate procurement activities must be provided for critical items, long lead items, items requiring Government approval and material/equipment procurement for which payment will be requested in advance of installation. Show each delivery with relationship tie to the Construction Activity specifically for the delivery.

1.10.1.5.4 Government Activities

Government and other agency activities that could impact progress must be clearly identified. Government activities include, but are not limited to; Government approved submittal reviews, Government conducted

SECTION 01 32 17.00 20 Page 7 inspections/tests, environmental permit approvals by State regulators, utility outages, Design Start, Construction Start (including Design/Construction Start for each Fast-Track Phase, and delivery of Government Furnished Material/Equipment.

1.10.1.5.5 Construction Quality Management (CQM) Activities

The Preparatory and Initial Phase meetings for each Definable Feature of Work identified in the Contractor's Quality Control Plan must be included in the Three-Week Look Ahead Schedule. Preparatory and Initial phase meetings are not required in the NAS, but can be represented by a start milestone linked to successor parent Construction Activity. The Follow-up Phase must be represented by the Construction Activities themselves in the

NAS.

1.10.1.5.6 Construction Activities

On-site construction activities that are the responsibility of the Contractor or Contractor's subcontractors must not have a duration in excess of 20 working days without prior approval by the Contracting Officer. Contractor activities must be driven by calendars that reflect Saturdays, Sundays and all Federal Holidays as non-work days, unless otherwise defined in this contract. Federal Holidays are as defined in 5

USC 6103.

1.10.1.5.7 Turnover and Closeout Activities

Include activities or milestones for items on the NAVFAC Red Zone Checklist/POAM that are applicable to this project. As a minimum, include required Contractor testing, required Government acceptance inspections on equipment, Pre-Final Inspection, Punch List Completion, Final Inspection and Acceptance. Add an unconstrained start milestone for the initial NAVFAC Red Zone - Facility Turnover Planning Meeting at approximately 75 percent construction contract completion or six months prior to Contract Completion Date (CCD), whichever is sooner. Include a separate NAVFAC Red Zone - Facility Turnover Planning Meeting Milestone for each phase if the contract requires construction to be completed in phases.

1.10.1.6 Contract Milestones and Constraints

1.10.1.6.1 Project Start Date Milestones

Include as the first activity on the schedule a start milestone titled, "Contract Award", which must have a Mandatory Start constraint equal to the Contract Award Date.

1.10.1.6.1.1 Design Phase Completion Milestone

Include an unconstrained finish milestone on the schedule titled, "Design Phase Completion". Design Phase Completion is defined as the point in time when all design requirements are complete and approved. Duration for Government review and approval must be included as predecessor activities to Design Phase Completion.

1.10.1.6.1.2 Post-Award Kickoff (PAK) meeting Milestone

Include an unconstrained finish milestone on the schedule titled, "Post-Award Kickoff Meeting". The Post Award Kickoff Meeting may be a single day, or it may range over several days. The intent is to cover all

SECTION 01 32 17.00 20 Page 8

PAK topics, including Partnering and Concept Design Workshop (if required) in one continuous session.

1.10.1.6.2 Preconstruction Submittals Finish Milestone

Include an unconstrained finish milestone on the schedule titled, "Preconstruction Submittals". This milestone is complete when all required preconstruction submittals have been reviewed and approved by the Government.

1.10.1.6.3 Contractor Mobilization Finish Milestone

Include an unconstrained finish milestone on the schedule titled, "Contractor Mobilization".

1.10.1.6.4 NAVFAC Red Zone - Facility Turnover Planning Meeting Milestones

See paragraph TURNOVER AND CLOSEOUT ACTIVITIES above.

1.10.1.6.5 Substantial Completion Milestone

Include an unconstrained finish milestone on the schedule titled "Substantial Completion." Substantial Completion is defined as the point in time the Government would consider the project ready for beneficial occupancy wherein by mutual agreement of the Government and Contractor, Government use of the facility is allowed while construction access continues in order to complete remaining items (e.g., punch list and other close out submittals). Include a separate Substantial Completion Milestone for each phase if the contract requires construction to be completed in phases.

1.10.1.6.6 DD-1354 Finish Milestone

Add unconstrained finish milestone, titled "DD-1354" and scheduled 30 calendar days prior to Substantial Completion, whenever a Form DD-1354 is required in accordance with Section 01 20 00 PRICE AND PAYMENT PROCEDURES. Include a separate DD-1354 Finish Milestone for each phase if the contract requires construction to be completed in phases.

1.10.1.6.7 Projected Completion Milestone

Include an unconstrained finish milestone on the schedule titled "Projected Completion." Projected Completion is defined as the point in time all contract requirements are complete and verified by the Government with a successful Final Inspection in accordance with Section 01 45 00.00 22 QUALITY CONTROL. This milestone must have the Contract Completion Date (CCD) milestone as its only successor.

1.10.1.6.8 Contract Completion Date (CCD) Milestone

Last schedule entry must be an unconstrained finish milestone titled "Contract Completion (CCD: DD-MM-YY)." DD-MM-YYYY is the current contract completion date at data date, day-month-year corresponding to P6 Must Finish By Date. NAS milestone updates of Project Completion finish date for longest path must reflect calculated float as positive or negative based on CCD. Calculation of schedule updates must be such that if the finish of the "Projected Completion" milestone falls after the contract completion date, then negative float is calculated on the longest path.

If the finish of the "Projected Completion" milestone falls before the

SECTION 01 32 17.00 20 Page 9 contract completion date, the float calculation must reflect positive float on the longest path.

1.10.1.6.9 Additional Milestones

Provide up to 5 additional milestones as required by Contracting Officer.

1.10.1.7 Work Breakdown Structure & Activity Code

At a minimum, establish a Work Breakdown Structure (WBS) and provide activity codes identified as follows:

1.10.1.7.1 Work Breakdown Structure (WBS)

Group all activities and milestones within appropriate WBS elements/levels including, at a minimum, the following:

a. Project Milestones:

(1) Management Milestones

(2) Project Administrative Meetings

(3) Permits

(4) Design Phase

(5) Submittals and Reviews

b. Pre-Construction Phase:

(1) Submittals and Reviews

(2) Procurement

(3) Mobilization

c. Construction Phase: Create multiple elements/levels in accordance with project specific definable features of work including in WBS descending order as follows:

(1) General Area

(a) Type of Work Item

1. Location

d. Project Closeout: Include activity items such as, but not limited to, Punchlist, Demobilization, O&M, As-built Drawings, Training, and As-built NAS.

e. Modifications: Create Conformed and Non-Conformed elements/levels under Modification WBS. Create multiple elements/levels as the project progresses identified by issue and Fragnet placed in Conformed for modifications issued prior data date, or Non-Conformed for issues not modified to contract prior data date.

f. Removed Activity: Activity is "removed" by remaining within logic sequence, eliminating duration and adding "(NO LONGER REQUIRED)" after

SECTION 01 32 17.00 20 Page 10

Activity Name in Activity Table.

1.10.1.7.2 Responsibility Code

Use "RESP" for Activity Code Name. All activities in the project schedule must be identified with the resource for completing the task. Activities must not belong to more than one responsible party.

1.10.1.7.3 Activity Category Code

Use "CAT" for Activity Code Name for the following Project Level activity codes:

a. Assign "PROC" value to Procurement type activity

b. Assign "PRE-CON" value to Pre-construction activity

c. Assign "CONS" value to Construction type activity

d. Assign "TEST" value to dedicated testing type activities

e. Assign "CX" value to dedicated Commissioning type activities

f. Assign "CLOS" value to dedicated Close Out type activity

g. Assign "OTHR" to other activity not otherwise designated

h. Assign "DSGN" value to Design type activity

1.10.1.8 Adverse Weather Lost Work Days

Use the National Oceanic and Atmospheric Administration's (NOAA) Summary of Monthly Normals report to obtain the historical average number of days each month with precipitation, using a nominal 30-year, greater than 0.10 inch precipitation amount parameter, as indicated on the Station Report for the NOAA location closest to the project site as the basis for establishing a "Weather Calendar" showing the number of anticipated non-workdays for each month due to adverse weather, in addition to Saturdays, Sundays and all Federal Holidays as non-work days.

Assign the Weather Calendar to any activity that could be impacted by adverse weather. The Contracting Officer will issue a modification in accordance with the contract clauses, giving the Contractor a time only extension for the difference of days between the anticipated and actual adverse weather delay if the number of actual adverse weather delay days exceeds the number of days anticipated for the month in which the delay occurs and the adverse weather delayed activities are on the longest path to contract completion in the period when delay occurred. A lost workday due to weather conditions is defined as a day in which the Contractor cannot work at least 50 percent of the day on the impacted activity.

Impacts resulting from adverse weather must be documented in Narrative Report for the month that it occurred.

Make changes to P6 project calendars to reflect as-built conditions where work occurred where originally anticipated as non-work days, and where work did not occur (lost work day).

SECTION 01 32 17.00 20 Page 11

1.10.1.9 Cost Loading

The Project Network Analysis Schedule (NAS) must be cost-loaded and will provide the basis for progress payments. Earned Value Reports must be derived from and correspond to cost loaded NAS. Use the Critical Path Method (CPM) and the Precedence Diagram Method (PDM) to satisfy time and cost applications.

Sum of all costs assigned to activities must equal the current contract value as of the data date of the baseline or update schedule.

1.10.1.9.1 Cost Loading Activities

Assign material and equipment costs, including their quantities, for which payment will be requested in advance of installation, to their respective procurement activity only for those material and equipment costs pre-approved by the Government. Assign labor costs, including their quantities, for material and equipment paid for after installation to their respective construction activities. Include all typical mobilization costs dispersed over early construction activities. Costs for mobilization will not be paid as individual pay items with the exception of batch plant set-up, mobilization of dredging equipment or other similar labor-intensive situations. Disperse submittal costs for activities referenced in paragraph PRE-CONSTRUCTION ACTIVITIES over all construction activities. The value of commissioning, testing and closeout WBS section may not be less than 10 percent of the total costs for procurement and construction activities. ALL activities assigned Government responsibility will have Zero Cost. No contractor cost should be assigned to an activity designated as a Government responsibility. Do not include field overhead positions as individual pay items. Evenly disperse overhead costs and profit to each activity over the duration of the actual construction activities assigned to the Construction Phase WBS level.

1.10.1.9.2 Partial Payment

Breakdown unit of measure and cost must be defined within P6 Activity Detail Expenses for partial payment of any cost loaded activity. Lump sum cost loaded activity will not be partially paid.

1.10.2 Schedule Software Settings and Restrictions

a. Activity Constraints: Date/time constraint(s), other than those required by the contract, are not allowed unless accepted by the Contracting Officer. Identify any constraints proposed and provide an explanation for the purpose of the constraint in the Narrative Report as described in paragraph REQUIRED TABULAR REPORTS.

b. Default Progress Data Disallowed: Actual Start is date work begins on activity with intent to pursue work to substantial completion. Actual Finish is date work is substantially complete to point where successor activity can begin. Actual dates on the CPM schedule must correspond with activity dates reported on the Contractor Quality Control and Production Reports.

c. At a minimum, include the following settings and parameters in P6 Schedule preparation:

(1) General: Define or establish Calendars and Activity Codes at the

SECTION 01 32 17.00 20 Page 12

"Project" level, not the "Global" level.

(2) Admin Drop-Down Menu, Admin Preferences, Time Periods Tab:

(a) Set time periods for P6 to 8.0 Hours/Day, 40.0 Hours/Week,

172.0 Hours/Month and 2000.0 Hours/Year.

(b) Use assigned calendar to specify the number of work hours for each time period: Must be checked.

(3) Admin Drop-Down Menu, Admin Preferences, Earned Value Tab:

(a) Technique for computing performance percent complete: Use "Activity percent Complete"

(b) Technique for computing Estimate to Complete: Use "PF = 1".

(c) Earned Value Calculation: Use "Budgeted values with current dates".

(4) Project Level, Dates Tab:

(a) Set "Must Finish By" date to "Contract Completion Date", and set "Must Finish By" time to 05:00pm.

(5) Project Level, Defaults Tab:

(a) Duration Type: Set to "Fixed Duration & Units".

(b) Percent Complete Type: Set to "Physical".

(c) Activity Type: Set to "Task Dependent".

(d) Calendar: Set to "Standard 5 Day Workweek". Calendar must reflect Saturday, Sunday and all Federal holidays as non-work days. Alternative calendars may be used with Contracting Officer approval.

(6) Project Level, Calculations Tab:

(a) Default Price/Unit for activities without resource or role Price/Units: Set to "$1/h".

(b) Activity percent complete based on activity steps: Must be Checked.

(c) Link Budget and At Completion for not started activities:

Must be Checked.

(d) Reset Remaining…