Technical Exhibit B Pavement Infrastructure Specs 25Jan24.pdf

Project Table of Contents Page 1

Fort Johnson Pavement and Infrastructure (25 Jan 24)

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 QUALITY CONTROL

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 20.00 10 ENVIRONMENTAL PROTECTION

01 57 23 TEMPORARY STORM WATER POLLUTION CONTROL

01 62 35 RECYCLED / RECOVERED MATERIALS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 32 00 SUBSURFACE DRILLING, SAMPLING, AND TESTING

02 41 00 DEMOLITION

DIVISION 03 - CONCRETE

03 11 13.00 10 STRUCTURAL CAST-IN-PLACE CONCRETE FORMING

03 20 00.00 10 CONCRETE REINFORCING

03 31 01.00 10 CAST-IN-PLACE STRUCTURAL CONCRETE FOR CIVIL WORKS

03 35 00.00 10 CONCRETE FINISHING

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 11 00 CLEARING AND GRUBBING

31 23 00.00 20 EXCAVATION AND FILL

DIVISION 32 - EXTERIOR IMPROVEMENTS

11.51

RUBBER AND PAINT REMOVAL FROM AIRFIELD PAVEMENTS

32 01 16.17 COLD MILLING OF BITUMINOUS PAVEMENTS

32 01 17.16 SEALING OF CRACKS IN BITUMINOUS PAVEMENTS

FIELD MOLDED SEALANTS FOR SEALING JOINTS IN RIGID

PAVEMENTS

GRADED-CRUSHED AGGREGATE BASE COURSE

32 11 29 LIME-STABILIZED SUBGRADE

32 11 33 CEMENT STABILIZED SUBBASE COURSE

32 12 10 BITUMINOUS TACK AND PRIME COATS

32 12 15.13 HOT-MIX ASPHALT AIRFIELD PAVING

32 12 16 HOT-MIX ASPHALT (HMA) FOR ROADS

32 13 11 CONCRETE PAVEMENT FOR AIRFIELDS AND OTHER HEAVY-DUTY

PAVEMENTS

32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE

FACILITIES

32 13 73 COMPRESSION JOINT SEALS FOR CONCRETE PAVEMENTS

SECTION 01 11 00 Page 2

Fort Johnson Pavement and Infrastructure

32 15 00 AGGREGATE SURFACE COURSE

32 16 13 CONCRETE SIDEWALKS AND CURBS AND GUTTERS

32 17 24.00 10 PAVEMENT MARKINGS

32 31 13.53 HIGH-SECURITY CHAIN LINK FENCES AND GATES

32 31 13 CHAIN LINK FENCES AND GATES

32 32 23 SEGMENTAL CONCRETE BLOCK RETAINING WALL

32 92 19 SEEDING

32 92 23 SODDING

DIVISION 33 - UTILITIES

33 40 00 STORM DRAINAGE UTILITIES

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 31 19.20 ARTICULATING CONCRETE BLOCK REVETMENTS

-- End of Project Table of Contents --

SECTION 01 11 00 Page 1

SECTION 01 11 00

SUMMARY OF WORK

08/21

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The Contractor shall furnish all labor, materials, equipment, and perform all work for the construction of pavement and drainage infrastructure, installation and/or repair (construction) as described in the general statement of work and task order statement of work and drawings at various locations at Fort Johnson, Louisiana, to include maneuver areas in strict accordance with the specifications and any incidental work incurred during construction. Upon completion the Contractor shall provide the Government with a complete and useable product. The government reserves the right to accept completion once the contractor provides a complete and usable product in accordance with the Task Order and specifications for the project.

1.1.2 Location

The exact location shall be defined with each Task Order.

1.5 OCCUPANCY OF PREMISES

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

Before work is started, arrange with the Project Delivery Team (PDT) a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.

1.6 EXISTING WORK

In addition to FAR 52.236-9 Protection of Existing Vegetation, Structures, Equipment, Utilities, and Improvements:

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

b. Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the PDT at the completion of operations.

SECTION 01 11 00 Page 2

1.8 LOCATION OF UNDERGROUND UTILITIES

Contractor shall locate and verify existing utilities in accordance with the task order and specs. Contractor shall obtain digging permits prior to start of excavation and comply with Installation requirements for locating and marking underground utilities. Contact local utility locating service a minimum of 48 hours prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on Task Order drawings, within area of work.

Contractor shall identify and mark all other utilities not managed and located by the local utility companies. Scan the construction site with Ground Penetrating Radar (GPR), electromagnetic, or sonic equipment, and mark the surface of the ground or paved surface where existing underground utilities are discovered.

Contractor shall verify the elevations of existing piping, utilities, and any type of underground obstruction not indicated, or specified to be removed, that is indicated or discovered during scanning, in locations to be traversed by piping, ducts, and other work to be conducted or installed. Verify elevations before installing new work closer than nearest manhole or other structure at which an adjustment in grade can be made.

1.8.1 Notification Prior to Excavation

Notify the Project Delivery Team at least 15 days prior to starting excavation work.

1.9 GOVERNMENT-FURNISHED MATERIAL

The Government may furnish materials for installation by the Contractor as described in each Task Order.

1.9.1 Delivery Schedule

Notify the PDT in writing at least 5 calendar days in advance of the date on which the materials are required. Pick up materials no later than 30 calendar days after such date.

1.9.2 Delivery Location

The materials location shall be coordinated through the PDT.

1.12 SALVAGE MATERIAL AND EQUIPMENT

Items designated by the PDT to be salvaged remain the property of the Government. Segregate, itemize, deliver, and off-load the salvaged property at the Government designated storage area located within 10 miles of the construction site. Contractor shall maintain property control records for material or equipment designated as salvage.

Contractor's system of property control may be used if approved by the PDT. Contractor shall be responsible for storage and protection of salvaged materials and equipment until disposition by the PDT.

SECTION 01 11 00 Page 3

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 30 00 Page 1

Part 1 GENERAL

1.1 REFERENCES

SECTION 01 30 00

Administrative Requirements

08/21

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2014) Safety -- Safety and Health Requirements Manual

U.S. NATIONAL ARCHIVES AND RECORDS ADMINISTRATION (NARA)

15 CFR 772 Definition of Terms

15 CFR 773 Special Licensing Procedures

1.2 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

View Location Map; G

Progress and Completion Pictures; G

1.3 VIEW LOCATION MAP

Submit to the PDT, 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.5 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 PDF 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 requested by the Project Delivery Team. Submit with the

SECTION 01 30 00 Page 2 monthly invoice two sets of digital photographs, each set on approved electronic media, 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 through approved media as a digital file. Include a date designator in file names. Each photograph shall contain a short description of what activity is being captured. Cross reference submittals in the appropriate daily report. Photographs shall be provided for unrestricted use by the Government.

1.6 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage required by FAR 28.307-2 Liability, during the entire period of performance for applicable Task Orders.

Provide other insurance coverage as required by State law.

1.7 SUPERVISION - Superintendent

1.7.1 Superintendent Qualifications

Contractor shall provide a superintendent with a minimum of 10 years’ experience in construction with at least 5 of those years as a superintendent on projects similar in size and scope. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent.

The Contractor shall submit proof of the superintendent's qualifications to the PDT by providing a resume.

1.7.2 Minimum Communication Requirements

Have at least one qualified superintendent, or superintendent’s alternate, capable of reading, writing, and conversing fluently in the English language, on the jobsite at all times during the performance of Task Order work. In addition, if a QC representative is required on the task order, then that individual must also have fluent English communication skills.

1.7.3 Duties

The 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 each Task Order until the work is completed and accepted.

1.7.4 Non-Compliance Actions

The Superintendent is subject to removal by the KO for non- compliance with requirements specified in the Task Order and for failure to manage the project to ensure timely completion. Furthermore, the KO may issue an order stopping all or part of the work until satisfactory corrective action has been taken.

SECTION 01 30 00 Page 3

1.8 PRECONSTRUCTION MEETING CONFERENCE

Immediately after award of each Task Order (prior to commencing any work at the site), the KO will coordinate a time and place to meet for the Preconstruction Meeting Conference. The meeting conference must take place after award of the Task Order, but within 10 days prior to commencement of any work at the site. The Preconstruction Meeting Conference must be immediately following the NTP meeting. The purpose of this meeting conference is to discuss and develop a mutual understanding of the administrative requirements of the Task Order 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 Task Order close-out. Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.

1.8.1 Attendees

Contractor should consider that attendees of the Preconstruction Meeting Conference include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.

Government attendees shall include necessary members of the PDT and advisory personnel as necessary.

1.9 NOTICE TO PROCEED (NTP) MEETING

Immediately after award, the KO will coordinate with a time and place for the NTP Meeting. The NTP meeting must be held within 30 calendar days after Task Order and each subsequent Task Order award and prior to commencing work. If mutually agreed upon by the Contractor and the Government, the NTP Meeting shall be held concurrently with the Preconstruction Meeting Conference.

1.9.1 NTP Meeting Outcomes

a. Integrate the Contractor and all client representatives into the project team.

b. Achieve consensus from the project team on any issues and concerns with the Contractor's technical proposal and the User's functional requirements. Confirm the work plan is within the project budget.

c. Review the administrative requirements of the Task Order that are critical during the submittal phase.

d. Establish clear lines of communication and points of contact for Government and PDT members.

e. Establish an understanding of administrative procedure for each Task

Order to be awarded under contract.

f. Review the project schedule and work plan requirement, submittal packaging, and preliminary construction schedule in accordance with Task Order documents. Discuss milestones and events that shall be included in the Quality Control Communication Plan.

g. Establish clear expectations and schedules for facility turnover, SECTION 01 30 00 Page 4 providing DD Form 1354 asset management records, submittals, Guiding Principal Validation, Third Party Certification (if applicable), and training of Government maintenance personnel.

h. Establish procedure for design packages reviews, Contractor's resolution to comments, and Government's role in review of packages.

1.14 PARTNERING

Contractor shall host the partnering session within 45 calendar days of Task Order award. To accomplish this Task Order, the Contractor and Government must form a cohesive partnership most effectively 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 Task Order documents and Specifications, within budget and on schedule. The partnering team must consist of personnel from both the Government and Contractor including project level and corporate level leadership positions. Key Personnel from the supported command, end user, Contractor, and key subcontractors are required to participate in the Partnering process.

1.14.2 Team-Led (Informal) Partnering

a. The PDT shall coordinate the initial Team-Led (Informal) Partnering Session with key personnel of the project team, including Contractor and Government personnel.

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

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

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

1.15 AVAILABILITY OF CADD DRAWING FILES

After award and upon request, the electronic "Computer-Aided Drafting and Design (CADD)" drawing files shall only be made available to the Contractor for use in preparation of construction data related to the referenced Task Order subject to the following terms and conditions.

Data contained on these electronic files shall not be used for any purpose other than as a convenience in the preparation of construction data for the referenced project. Any other use or reuse shall be at the sole risk of the Contractor and without liability or legal exposure to the Government. The Contractor shall make no claim and waives to the fullest extent permitted by law, any claim or cause of action of any nature against the Government, its agents or sub consultants that may arise out of or in connection with the use of these electronic files. The Contractor shall, to the fullest extent permitted by law, indemnify and hold the Government harmless against all damages, liabilities or costs, including reasonable attorney’s fees and

SECTION 01 30 00 Page 5 defense costs, arising out of or resulting from the use of these electronic files.

These electronic CADD drawing files are not construction documents.

Differences may exist between the CADD files and the corresponding construction documents. The Government makes no representation regarding the accuracy or completeness of the electronic CADD files, nor does it make representation to the compatibility of these files with the Contractors hardware or software. In the event that a conflict arises between the signed and sealed construction documents prepared by the Government and the furnished CADD files, the signed and sealed construction documents shall govern. The Contractor is responsible for determining if any conflict exists. Use of these CADD files does not relieve the Contractor of duty to fully comply with the Task Order documents, including and without limitation, the need to check, confirm and coordinate the work of all contractors for the project.

If the Contractor uses, duplicates and/or modifies these electronic CADD files for use in producing construction drawings and data related to this Task Order, all previous indicia of ownership (seals, logos, signatures, initials and dates) shall be removed.

1.16 ELECTRONIC MAIL (E-MAIL) ADDRESS

The Contractor shall establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments in Microsoft, Adobe Acrobat, and other similar formats. Within 10 days after Task Order award, the Contractor shall provide the PDT a single (only one) e-mail address for electronic communications from the PDT related to this Task Order including, but not limited to Task Order documents, invoice information, request for proposals, and other correspondence. The Project Delivery Team may also use email to notify the Contractor of base access conditions when emergency conditions warrant, such as hurricanes, terrorist threats, etc. Multiple email address will not be allowed.

It is the Contractor's responsibility to make timely distribution of all PDT initiated e-mail with its own organization including field office(s). The Contractor shall promptly notify the PDT, in writing, of any changes to this email address.

Not Used

SECTION 01 32 01.00 10. Page 6

SECTION 01 32 01.00

10 PROJECT SCHEDULE

02/15

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

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

Applied in Construction

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (2017) Administration -- Project Schedules

1.2 SUBMITTALS

classification. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler

Qualifications; G Preliminary

Project Schedule; G Initial

Project Schedule; G Periodic

Schedule Update; G

Not

Used PART 3

EXE

CUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for each Task Order, as specified herein, pursuant to the contract clause, SCHEDULE FOR CONTRUCTION CONTRACTS. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing

SECTION 01 32 01.00 10. Page 7 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 to developing and maintaining an accurate Project Schedule. Provide a schedule that is forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules. Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract Bid Item must equal the value of the Bid Item.

3.2.1 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 PDT directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the KO may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Project Delivery Team will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

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

3.3.4 Procurement Activities

The Schedule must 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 8

3.3.5 Mandatory Tasks

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

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

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

c. Long procurement activities

d. Submission and approval of O & M manuals.

e. Submission and approval of as-built drawings.

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

g. Performance Verification testing.

h. Other systems testing, if required.

i. Contractor's pre-final inspection.

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

k. Government's pre-final inspection.

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

m. Final inspection.

3.3.6 Government Activities

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

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

3.3.7 Standard Activity Coding Dictionary

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

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work http://rms.usace.army.mil/

SECTION 01 32 01.00 10. Page 9

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

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

3.3.7.1 Workers Per Day (WRKP)

Assign Workers per Day for all field construction or direct work activities, if directed by the Project Delivery Team. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

3.3.7.2 Responsible Party Coding (RESP)

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and 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.

3.3.7.3 Area of Work Coding (AREA)

Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew from working in more than one work area at a time due to restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings.

Activities cannot have more than one Work Area Code.

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

3.3.7.4 Modification Number (MODF)

SECTION 01 32 01.00 10. Page 10

Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Task Order Modification, when approved by Project Delivery Team. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.3.7.5 Bid Item Coding (BIDI)

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

3.3.7.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are 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 Task Order specifies phasing with separately defined performance periods, identify a Phase Code to allow filtering and organizing the schedule accordingly.

3.3.7.7 Feature of Work Coding (FOW)

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

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

3.3.8 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited. No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the PDT and Government PM for approval on a case-by-case basis.

3.3.8.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged.

SECTION 01 32 01.00 10. Page 11

3.3.8.2 End Project Finish Milestone and Constraint

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

Constrain the project schedule to the Task Order Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

3.3.8.3 Interim Completion Dates and Constraints

Constrain contractually specified interim completion dates to show negative float when the calculated late finish date of the last activity in that phase is later than the specified interim completion date.

3.3.8.3.1 Start Phase

Use a start milestone as the first activity for a project phase.

Call the start milestone "Start Phase X" where "X" refers to the phase of work.

3.3.8.3.2 End Phase

Use a finish milestone as the last activity for a project phase.

Call the finish milestone "End Phase X" where "X" refers to the phase of work.

3.3.9 Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any Task Order 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. Develops Seasonal Calendar(s) and assign to seasonally affected activities as applicable.

If an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated adverse weather delay work days provided in the Special Task Order Requirements. 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.

3.3.10 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 Project Delivery Team’s approval.

SECTION 01 32 01.00 10. Page 12

3.3.11 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

3.3.12 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by- case basis subject to approval by the Project Delivery Team.

Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.3.13 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the Project Delivery team. Activity ID and description changes are considered new activities and cannot be changed without Project Delivery Team approval.

3.3.14 Original Durations

Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Project Delivery Team.

3.3.15 Leads, Lags, and Start to Finish Relationships

Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

b. Start to Finish (SF) relationships are prohibited.

3.3.16 Retained Logic

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

SECTION 01 32 01.00 10. Page 13

3.3.17 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management.

3.3.18 Remaining Duration

Update the remaining duration for each activity based on the number of estimated work days it will take to complete the activity.

Remaining duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete.

3.3.19 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the present contract value. Activity(ies) may be declared 100 percent complete upon the Government's verification of completion and correction of all punch list work identified during Government pre-final inspection(s).

3.3.19.1 As-Built Drawings

If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than $35,000 or 1 percent of the present contract value, which ever is greater, up to $200,000.

Activity will be declared 100 percent complete upon the Government's approval.

3.3.19.2 O & M Manuals

Cost load the "Submission and approval of O & M manuals" activity not less than $20,000. Activity will be declared 100 percent complete upon the Government's approval of all O & M manuals.

3.3.20 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required Task Order work will be completed before the contractually required completion date.

a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.

b. The Government is under no obligation to accelerate work items it is responsible for to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are

SECTION 01 32 01.00 10. Page 14 contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.

Review comments made by the Government on the schedule(s) do not relieve the Contractor from compliance with requirements of the Task Order Documents.

3.4.1 Preliminary Project Schedule Submission

Within 15 calendar days after the NTP is acknowledged submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the Task Order award CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the Task Order (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period.

Also cover in the initial schedule the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed construction activities through the dry-in milestone, including all activity coding and cost loading. Include the remaining construction, including cost loading, but it may be scheduled summary in nature. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Periodic Schedule Updates

Update the Project Schedule on a regular basis, monthly at a minimum.

Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE

UPDATE

MEETINGS. These updates will enable the Government to assess Contractor's progress. If the Contractor fails or refuses to furnish the information and

SECTION 01 32 01.00 10. Page 15 project schedule data, which in the judgment of the Project Delivery Team or authorized representative is necessary for verifying the Contractor's progress, the Contractor shall be deemed not to have provided an estimate upon which progress payment may be made.

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the

Contractor's Quality Control Report for an activity start or finish.

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:

3.5.1 Data CD/DVDs

Provide two sets of data CD/DVDs containing the current project schedule and all previously submitted schedules in the format of the scheduling software. Also include on the data CD/DVDs the Narrative Report and all required Schedule Reports. Label each CD/DVD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule must have a unique file name and use project specific settings. Contractor should submit in writing for Government approval a change of medium request for electronic file submission.

3.5.2 Narrative Report

Provide a Narrative Report with the Preliminary, Initial, and each Periodic Update of the project schedule, as the basis of the progress payment request. The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for any problems, either current or potential, which are revealed through that analysis. Include the following information as minimum in the Narrative Report:

a. Identify and discuss the work scheduled to start in the next update period.

b. A description of activities along the two most critical paths where the total float is less than or equal to 20 work days.

c. A description of current and anticipated problem areas or delaying factors and their impact and an explanation of corrective actions taken or required to be taken.

d. Identify and explain why activities based on their calculated late dates should have either started or finished during the update period but did not.

e. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, SECTION 01 32 01.00 10. Page 16 lag changes, resource changes, and actual start and finish date changes.

f. Identify and discuss out-of-sequence work.

3.5.3 Approved Changes Verification

Include only those project schedule changes in the schedule submission that have been previously approved by the Project Delivery Team. The Narrative Report shall specifically reference, on an activity by activity basis, all changes made since the previous period and elate each change to documented, approved schedule changes.

3.5.4 Schedule Reports

The format, filtering, organizing, and sorting for each schedule report will be as directed by the Project Delivery Team. Typically, reports contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format.

Provide two (2) set(s) of hardcopy reports. The following lists typical reports that will be requested:

3.5.4.1 Activity Report

List of all activities sorted according to activity number.

3.5.4.2 Logic Report

List of detailed predecessor and successor activities for every activity in ascending order by activity number.

3.5.4.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.

3.5.4.4 Earnings Report by CLIN

A compilation of the Total Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein.

Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

SECTION 01 32 01.00 10. Page 17

3.5.5 Network Diagram

The Network Diagram is required for the Preliminary, Initial and Periodic Updates. Depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Project Delivery Team will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.5.1 Continuous Flow

Show a continuous flow from left to right with no arrows from right to left. Show the activity number, description, duration, and estimated earned value on the diagram.

3.5.5.2 Project Milestone Dates

Show dates on the diagram for start of project, any contract required interim completion dates, and Task Order completion dates.

3.5.5.3 Critical Path

Show all activities on the critical path. The critical path is defined as the longest path.

3.5.5.4 Banding

Organize activities using the WBS or as otherwise directed to assist in the understanding of the activity sequence. Typically, this flow will group activities by major elements of work, category of work, work area and/or responsibility.

3.5.5.5 Cash Flow / Schedule Variance Control (SVC) Diagram

With each schedule submission, provide an SVC diagram showing 1) Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates, and 2) Earned Value to-date.

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

Conduct periodic schedule update meetings for the purposes of reviewing the Contractor's proposed out of sequence corrections, determining causes for delay, correcting logic, maintaining schedule accuracy and determining earned value. Meetings shall occur at least monthly within five days of the proposed schedule data date and after the Contractor has updated the schedule with Government concurrence respecting actual start dates, actual finish dates, remaining durations and percent complete for each activity it intends to status. Provide a computer with the scheduling software loaded and a projector during the meeting which allows all meeting participants to view the proposed schedule update during the meeting. The meeting and resultant approvable schedule update shall be a condition precedent to a formal submission of the update as described in SUBMISSION REQUIREMENTS and to the submission of an invoice for payment. The meeting will be a working interactive exchange which will allow the Government and the Contractor the opportunity to review the updated schedule on a real time and interactive basis. The Contractor's authorized scheduling representative will organize, sort, filter and schedule the update as

SECTION 01 32 01.00 10. Page 18 requested by the Government. A rough draft of the proposed activity logic corrections and narrative report shall be provided to the Government 48 hours in advance of the meeting. The Contractor's Project Manager and Authorized Scheduler shall attend the meeting with members of the Project Delivery Team.

3.6.2 Update Submission Following Progress Meeting

Submit the complete Periodic Schedule Update of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 work days after the periodic schedule update meeting.

3.6.2.1 Status of Activities

Update information, including Actual Start Dates (AS), Actual Finish Dates(AF), Remaining Durations (RD), and Percent Complete shall be subject to the approval of the Government prior to the meeting. As a minimum, address the following items on an activity by activity basis during each progress meeting.

3.6.2.2 Start and Finish Dates

Accurately show the status of the AS and/or AF dates for each activity currently in-progress or completed since the last update.

The Government may allow an AF date to be assigned with the percent complete less than100% to account for the value of work remaining but not restraining successor activities. Only assign AS dates when actual progress occurs on an activity.

3.6.2.3 Remaining Duration

Update the estimated RD for all incomplete activities independent of Percent Complete. Remaining Durations may exceed the activity OD or may exceed the activity's prior update RD if the Government considers the current OD or RD to be understated based on current progress, insufficient work crews actually manning the job, unrealistic OD or deficiencies that must be corrected that restrain successor activities.

3.6.2.4 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete. To allow for proper schedule management, cost load the correction of punch list from Government pre-final inspection activity(ies) not less than 1 percent of the total Task Order value, which activity(ies) may be declared 100 percent complete upon completion and correction of all punch list work identified during Government pre-final inspection(s).

3.6.2.5 Logic Changes

Specifically identify and discuss all logic changes pertaining to NTP on change orders, change orders to be incorporated into the schedule, Contractor proposed changes in work sequence, corrections to schedule logic for out-of-sequence progress, and other changes that have been

SECTION 01 32 01.00 10. Page 19 made pursuant to contract provisions. The Government will only approve logic revisions for the purpose of keeping the schedule valid in terms of its usefulness in calculating a realistic completion date, correcting erroneous logic ties, and…