70LART19BPFB00003_FLETC_Artesia_Ranges_Specifications.pdf

SPECIFICATIONS

FEDERAL LAW ENFORCEMENT TRAINING CENTER

1300 W RICHEY AVE, ARTESIA, NM

ARTESIA BORDER PATROL 100 YARD AND 300 YARD

TACTICAL AWARENESS TRAINING RANGES

FINAL SUBMISSION

PREPARED BY

STV INCORPORATED

STV Project No. 30-19733 July 19, 2019

DHS Artesia Border Patrol 100-yard and 300-yard DHS Order No. 70LART18FPFB00l05 Tactical Awareness Training Ranges STV Project No. 3019733

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 29 Safety and Occupational Health Requirements 01 42 00 Sources for Reference Publications 01 45 04.00 10 Contract Quality Control 01 50 00.00 20 Temporary Facilities and Controls 01 57 19.00 20 Temporary Environmental Controls 01 62 35 Recycled / Recovered Materials 01 77 00.00 20 Closeout Procedures 01 78 23 Operation and Maintenance Data

Division 02 - Site Work

02 61 13 Excavation and Handling of Contaminate Material

Division 11 – Equipment 11 92 00 Target Equipment

Division 27 – Communications Section 27 51 16 Public-Address Systems

Division 31 – Earthwork Section

31 00 00 Earthwork 31 10 00 Clearing for Civil Works 31 23 00.00 20 Excavating and Fill

Division 32 – Exterior Improvements Section 32 15 00 Aggregate Surfacing

Division 33 – Utilities Section 33 40 00 Storm Drainage Utilities 33 71 02 Underground Electrical Distribution 33 82 00 Telecommunications Outside Plant (OSP)

This Page Intentionally Blank

DHS Artesia Border Patrol 100/300 Yards DHS Order No. 70LART18FPFB00105

SECTION 01 11 00 Page 1

SECTION 01 11 00

SUMMARY OF WORK

07/07

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes construction of converting two existing 50-yard rifle ranges (located at existing Range 5-East and Range 6-East) into a 100-yard real-terrain live-fire range and a 300-yard rifle flat range. Along with the design parameters for the two ranges, environmental considerations will include the development of an Environmental Analysis (EA), and proposed Action and Alternatives (DOPAA).

The site that was chosen for this project is in Artesia, New Mexico at the Federal Law Enforcement Training Center. The ranges are currently, and will continue to be, protected by a perimeter fence which will need to be modified to accommodate the longer proposed ranges.

Both the 100-yard real-terrain live-fire range and the 300-yard rifle flat range will be constructed with sustainable materials to achieve high durability and low maintenance range operations and equipment.

1.1.2 Location

The work shall be located at the Federal Law Enforcement Training Center Firing Range, Artesia, New Mexico, approximately as indicated.

1.2 Bid Options

The project is segregated into a base bid with multiple bid options. The government will select bid options in sequential order as follows:

1.2.1 Base Bid: Complete project excluding Bid Options. Note: All work associated with the targetry (target emplacement wall/berns, pads, utilities, etc.) are included in the base bid.

1.2.2 Bid Option No.1: Range 5 – 25 turning targets at 100-yard marker

1.2.3 Bid Option No.2: Range 5 – 12 popup targets at 200-yard marker

1.2.4 Bid Option No.4: Range 5 – Pea Gravel from Firing Line to 200-yard marker

1.2.5 Bid Option No.5: Range 5 – Pea Gravel from 200-yard marker to 300-yard marker

1.2.6 Bid Option No.6 Range 6 – 13 turning targets at 100-yard marker

1.3 LOCATION OF UNDERGROUND FACILITIES

Scan the construction site with electromagnetic or sonic equipment, and mark the surface of the ground where existing underground utilities are discovered. Verify the elevations of existing piping, utilities, and any type of underground obstruction not indicated to be specified or removed but indicated or discovered during scanning in locations to be traversed by

SECTION 01 11 00 Page 2 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.3.1 Notification Prior to Excavation

Notify the Contracting Officer at least 15 days prior to starting excavation work.

1.4 TYPE OF CONTRACT

1. Project will be constructed under a single prime contract.

1.5 WORK BY OWNER

None.

1.6 WORK UNDER SEPARATE CONTRACTS

None.

1.7 OWNER-FURNISHED PRODUCTS

Owner will furnish products indicated. The Work includes receiving, unloading, handling, storing, protecting, and installing Owner-furnished products and making building services connections.

A. Range 6 Tactical Vehicles

1.8 ACCESS TO SITE

1.8.1 General: Contractor shall have limited use of Project site for construction operations as indicated on Drawings by the Contract limits and as indicated by requirements of this Section.

1.8.2 Use of Site: Limit use of project site to work in areas indicated. Do not disturb portions of project site beyond areas in which the work is indicated and infrastructure within project limits that must be preserved during construction.

1.8.3 Driveways, Walkways and Entrances: Keep driveways loading areas, and entrances serving premises clear and available to Owner, Owner's employees, and emergency vehicles at all times. Do not use these areas for parking or storage of materials.

1.8.4 Schedule deliveries to minimize use of driveways and entrances by construction operations.

1.9 COORDINATION WITH OCCUPANTS

1.9.1 Partial Owner Occupancy: Owner will occupy the adjacent firing ranges during entire construction period. Cooperate with the Owner during construction operations to minimize conflicts and facilitate Owner

SECTION 01 11 00 Page 3 usage. Perform the Work so as not to interfere with Owner's operations.

1.9.2 Provide not less than [72 hours] notice to Owner of activities that will affect Owner's operations.

1.9. WORK RESTRICTIONS

1.9.1 On-Site Work Hours: Limit work to working hours of 7:00 a.m. to 4:00 p.m., Monday through Friday, unless otherwise indicated.

1.9.2 Weekend Hours: Coordinate with Owner.

1.9.3 Hours for Utility Shutdowns: Coordinate with Owner.

1.9.4 Existing Utility Interruptions: Do not interrupt utilities serving facilities occupied by Owner or others unless permitted under the following conditions and then only after providing temporary utility services according to requirements indicated:

1.9.5 Notify Owner not less than five days in advance of proposed utility interruptions.

1.9.6 Obtain Owner's written permission before proceeding with utility interruptions.

1.9.7 Noise, Vibration, and Odors: Coordinate operations that may result in high levels of noise and vibration, odors, or other disruption to Owner occupancy with Owner.

1.9.8 Notify Owner not less than five days in advance of proposed disruptive operations.

1.9.9 Obtain Owner's written permission before proceeding with disruptive operations.

1.9.10 Controlled Substances: Use of tobacco products is regulated by the Owner. Use of other controlled substances on Project site is not permitted.

1.9.11 Employee Identification: Owner will provide identification tags for Contractor personnel approved for work on Project site. Contractor’s personnel are required to carry identification tags at all times.

1.9.12 Employee Screening: Comply with Owner's requirements for access card of Contractor personnel working on Project site.

1.9.13 Maintain list of approved screened personnel with Owner's representative.

1.10. SEQUENCE OF CONSTRUCTION

1.10.01 The governments existing ranges will remain in operation throughout

SECTION 01 11 00 Page 4 the construction duration of Range 5 and Range 6. Therefore, to provide additional ballistic protection during construction of the new ranges, the contractor shall construct Range 5’s western ballistic berm first, allowing additional protection for the contractor and the government on-site personnel during construction.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

-- End of Section --

SECTION 01 30 00 Page 1

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

04/07

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for Contractor Quality Control approval. The following shall be submitted in accordance with Section 01 33

00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of contact personnel; G OIC

Personnel list; G OIC

Vehicle list; G OIC

1.2 MINIMUM INSURANCE REQUIREMENTS

Procure and maintain during the entire period of performance under this contract the following minimum insurance coverage:

a. Comprehensive general liability: $500,000 per occurrence

b. Automobile liability: $200,000 per person, $500,000 per occurrence for bodily injury, $20,000 per occurrence for property damage

c. Workmen's compensation as required by Federal and State workers' compensation and occupational disease laws.

d. Employer's liability coverage of $100,000, except in States where workers compensation may not be written by private carriers,

e. Others as required by State law.

1.3 CONTRACTOR PERSONNEL REQUIREMENTS

1.3.1 Subcontractors and Personnel

Furnish a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.

SECTION 01 30 00 Page 2

1.3.2 Identification Badges

Identification badges, if required, will be furnished without charge.

Application for, and use of, badges will be as directed. Immediately report instances of lost or stolen badges to the Contracting Officer.

1.3.3 Subcontractor Special Requirements

1.3.3.1 Space Temperature Control and HVAC TAB

All contract requirements of Section Section 23 09 23.13 20 BACnet DIRECT DIGITAL CONTROL FOR HVAC and Section 23 08 00.00 20 HVAC TESTING/ADJUSTING/BALANCING shall be accomplished directly by a first tier subcontractor, including the Commissioning Agent. No work required by Section 23 09 23.13 20 or 23 08 00.00 20 shall be accomplished by a second tier subcontractor.

1.3.4 Contractor Personnel Requirements

Failure to obtain entry approval will not affect the contract price or time of completion.

1.3.5 Employment Restrictions

1.3.5.1 Personnel List

Submit for approval, at least 15 days prior to the desired date of entry, an original alphabetical list of personnel who require entry into Government property to perform work on the project. Furnish for each person:

a. Name

b. Date and place of birth

c. Citizenship

d. Home address

e. Social security number

f. Naturalization or Alien Registration number

The request for personnel passes shall be accompanied with the following certification:

"I hereby certify that all personnel on this list are either born U.S.

citizens, naturalized U.S. citizens with the naturalization number shown, or legal aliens with the alien registration number indicated."

Signature/Firm Name

1.3.5.2 Vehicle List

Submit an original list of vehicles to be utilized at the work site with the following information for each vehicle:

SECTION 01 30 00 Page 3

a. Make

b. Year

c. Model

d. License number

e. Registered owner

1.3.5.3 Passes

Submit request for personnel and vehicle passes together. Include the Certificate of Insurance for Contractor and Subcontractor(s).

1.3.5.4 Control

Maintain strict accountability over passes. Immediately report to the source of issue, passes missing or lost and the circumstances. If the Contractor has another active contract or one commencing immediately, employees' names may be transferred from one contract to the other. Final payment will not be effected until employees are transferred to another contract or the records are cleared. Furnish a signed letter, countersigned by the source of issue, stating that passes have been turned in.

Contractor's personnel shall stay within the limits of the temporary construction fence, except when approved by the COR to work in adjacent areas.

1.4 SUPERVISION

Have at least one qualified supervisor capable of reading, writing, and conversing fluently in the English language on the job site during working hours. In addition, if a Quality Control (QC) representative is required on the contract, then that individual shall also have fluent English communication skills.

1.5 PRECONSTRUCTION CONFERENCE

After award of the contract but prior to commencement of any work at the site, meet with the Contracting Officer to discuss and develop a mutual understanding relative to the administration of the value engineering and safety program, preparation of the schedule prices, shop drawings, and other submittals, scheduling programming, and prosecution of the work. Major subcontractors who will engage in the work shall also attend.

1.6 AVAILABILITY OF CADD DRAWING FILES

After award and upon request, the electronic "Computer-Aided Drafting and Design (CADD)" drawing files will only be made available to the Contractor for use in preparation of construction data related to the referenced contract 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

SECTION 01 30 00 Page 4 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 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 contract 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 data related to this contract, all previous indicia of ownership (seals, logos, signatures, initials and dates) shall be removed.

1.7 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 contract award, the Contractor shall provide the Contracting Officer a single (only one) e-mail address for electronic communications from the Contracting Officer related to this contract including, but not limited to contract documents, invoice information, request for proposals, and other correspondence. The Contracting Officer may also use email to notify the Contractor of site access conditions when emergency conditions warrant, such as hurricanes, terrorist threats, etc. Multiple email address will not allowed.

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

SECTION 01 30 00 Page 5

This Page Intentionally Blank

SECTION 01 32 01.00 10 Page 1

SECTION 01 32 01.00 10

PROJECT SCHEDULE

07/07

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)

ECB 2005-10 (2005) Scheduling Requirements for Testing of

Mechanical Systems in Construction

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

Analysis Systems

1.2 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for Contractor Quality Control

Project Schedule; G A/E

1.3 QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating (activity status) and preparation of reports. The authorized representative shall be experienced in scheduling projects similar in nature to this project and shall be experienced in the use of the scheduling software that meets the requirements of this specification.

PART 2 PRODUCTS (NOT APPLICABLE)

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. The scheduling of the entire project construction sequences is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel shall actively

SECTION 01 32 01.00 10 Page 2 participate in its development. Subcontractors and suppliers working on the project shall also contribute in developing and maintaining an accurate Project Schedule. The schedule must be a forward planning as well as a project monitoring tool.

3.1.1 Approved Project Schedule

Use the approved Project Schedule to measure the progress of the work and to aid in evaluating time extensions. Make the schedule cost loaded and activity coded. The schedule will provide the basis for all progress payments. If the Contractor fails to submit any schedule within the time prescribed, the Contracting Officer may withhold approval of progress payments until the Contractor submits the required schedule.

3.1.2 Schedule Status Reports

Provide a Schedule Status Report on at least a monthly basis. If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, the Contractor shall take steps necessary to improve its progress including those that may be required by the Contracting Officer, without additional cost to the Government. In this circumstance, the Contracting Officer may require the Contractor to increase the number of shifts, overtime operations, days of work, and/or the amount of construction plant, and to submit for approval any supplementary schedule or schedules as the Contracting Officer deems necessary to demonstrate how the approved rate of progress will be regained.

3.1.3 Default Terms

Failure of the Contractor to comply with the requirements of the Contracting Officer shall be grounds for a determination by the Contracting Officer that the Contractor is not prosecuting the work with sufficient diligence to ensure completion within the time specified in the contract. Upon making this determination, the Contracting Officer may terminate the Contractor's right to proceed with the work, or any separable part of it, in accordance with the default terms of the contract.

3.2 BASIS FOR PAYMENT AND COST LOADING

Use the schedule as the basis for determining contract earnings during each update period and therefore the amount of each progress payment. Lack of an approved schedule update or qualified scheduling personnel will result in an inability of the Contracting Officer to evaluate contract earned value for the purposes of payment. Failure of the Contractor to provide all required information will result in the disapproval of the preliminary, initial and subsequent schedule updates. In the event schedule revisions are directed by the Contracting Officer and those revisions have not been included in subsequent revisions or updates, the Contracting Officer may hold retainage up to the maximum allowed by contract, each payment period, until such revisions to the Project Schedule have been made. Activity cost loading shall be reasonable, as determined by the Contracting Officer. The aggregate value of all activities coded to a contract CLIN shall equal the value of the CLIN on the Schedule.

SECTION 01 32 01.00 10 Page 3

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

The computer software system utilized to produce and update the Project Schedule shall be capable of meeting all requirements of this specification.

Failure of the Contractor to meet the requirements of this specification will result in the disapproval of the schedule. Scheduling software that meets the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 are Primavera Project Planner (P3) by Primavera, and Open Plan by Deltek

3.3.1 Critical Path Method

Use the Critical Path Method (CPM) of network calculation to generate the Project Schedule. Prepare the Project Schedule using the Precedence Diagram Method (PDM).

3.3.2 Level of Detail Required

Develop the Project Schedule to an appropriate level of detail. Failure to develop the Project Schedule to an appropriate level of detail, as determined by the Contracting Officer, will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2.1 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 shall have Original Durations (OD) greater than 20 work days or 30 calendar days. Procurement activities are defined herein.

3.3.2.2 Procurement Activities

The schedule must include activities associated with the submittal, approval, 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. A typical procurement sequence includes the string of activities: submit, approve, procure, fabricate, and deliver.

3.3.2.3 Mandatory Tasks

The following tasks must be included and properly scheduled:

a. Submission, review and acceptance of design packages.

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

c. Submission and approval of O & M manuals.

d. Submission and approval of as-built drawings.

e. Submission and approval of 1354 data and installed equipment lists.

SECTION 01 32 01.00 10 Page 4

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

g. Submission of TAB specialist design review report.

h. Submission and approval of fire protection specialist.

i. Submission and approval of testing and balancing of HVAC plus commissioning plans and data. Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with ECB 2005-10.

j. Air and water balancing.

k. HVAC commissioning.

l. Controls testing plan submission.

m. Controls testing.

n. Performance Verification testing.

o. Other systems testing, if required.

p. Contractor's pre-final inspection.

q. Correction of punchlist from Contractor's pre-final inspection.

r. Government's pre-final inspection.

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

t. Final inspection.

3.3.2.4 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: approvals, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.2.5 Activity Responsibility Coding (RESP)

Assign responsibility Code for all activities to the Prime Contractor, Subcontractor or Government agency responsible for performing the activity.

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 Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements. Code all activities not coded with a Government Responsibility Code to the Prime Contractor or Subcontractor responsible to perform the work. Activities shall not have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record); ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for

SECTION 01 32 01.00 10 Page 5

FLETC). Unacceptable code values are abbreviations of the names of subcontractors.

3.3.2.6 Activity Work Area Coding

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 shall not have more than one Work Area Code. Not all activities are required to be Work Area coded. A lack of Work Area coding will indicate the activity is not resource or space constrained.

3.3.2.7 Contract Changes/Requests for Equitable Adjustment (REA) Coding

(MODF)

Assign Activity code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by the Contracting Officer, with a Contract Changes/REA Code. Key all Code values to the Government's modification numbering system. Any activity or sequence of activities added to the schedule as a result of alleged constructive changes made by the Government may be added to a copy of the current schedule, subject to the approval of the Contracting Officer. Assign Activity codes for these activities with a Contract Changes/REA Code. Key the code values to the Contractor's numbering system. Approval to add these activities does not necessarily mean the Government accepts responsibility and therefore liability for such activities and any associated impacts to the schedule, but rather the Government recognizes such activities are appropriately added to the schedule for the purposes of maintaining a realistic and meaningful schedule. Such activities shall not be Responsibility Coded to the Government unless approved. An activity shall not have more than one Contract Changes/REA Code.

3.3.2.8 Contract Line Item (CLIN) Coding (BIDI)

Code all activities to the CLIN on the Contract Line Item Schedule to which the activity belongs. An activity shall not contain more than one CLIN Item Code. CLIN Item code all activities, even when an activity is not cost loaded.

3.3.2.9 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities based upon the phase of work in which the activity occurs. Code activities to a Construction Phase. Code fast track construction phases proposed by the Contractor to allow filtering and organizing the schedule by fast track design and construction packages.

If the contract specifies construction phasing with separately defined performance periods, identify a Construction Phase Code to allow filtering and organizing the schedule accordingly. Each activity shall be identified with a single project phase and have only one Phase of Work code.

SECTION 01 32 01.00 10 Page 6

3.3.2.10 Category of Work Coding (CATW)

Assign Category of Work Code to all Activities based upon the category of work to which the activity belongs. Category of Work Code must include, but is not limited to: permits, construction submittal approvals, Acceptance, Procurement, Fabrication, Delivery, Weather Sensitive Installation, Non- Weather Sensitive Installation, Start-Up, Test and Turnover. Assign a Category of Work Code to each activity. Each activity shall have only one Category of Work Code.

3.3.2.11 Definable Features of Work Coding (FOW1, FOW2, FOW3)

Assign a Definable Feature of Work Code to appropriate activities based on the definable feature of work to which the activity belongs. Definable Feature of Work is defined in Specification Section 01 45 04.00 10 CONTRACTOR QUALITY CONTROL. An activity shall not have more than one Definable Feature of Work Code. Not all activities are required to be Definable Feature of Work Coded.

3.3.3 Scheduled Project Completion and Activity Calendars

The schedule interval shall extend from NTP date to the required contract completion date. The contract completion activity (End Project) shall finish based on the required contract duration in the accepted contract proposal, as adjusted for any approved contract time extensions. The first scheduled work period shall be the day after NTP is acknowledged by the Contractor. Schedule activities on a calendar to which the activity logically belongs. Activities may be assigned to a 7 day calendar when the contract assigns calendar day durations for the activity such as a Government Acceptance activity. If the Contractor intends to perform physical work less than seven days per week, schedule the associated activities on a calendar with non-work periods identified including weekends and holidays. Assign the Category of Work Code - Weather Sensitive Installation to those activities that are weather sensitive. Original durations must account for anticipated normal adverse weather. The Government will interpret all work periods not identified as non-work periods on each calendar as meaning the Contractor intends to perform work during those periods.

3.3.3.1 Project Start Date

The schedule shall start no earlier than the date on which the NTP was acknowledged. Include as the first activity in the project schedule an activity called "Start Project" (or NTP). The "Start Project" activity shall have an "ES" constraint date equal to the date that the NTP was acknowledged, and a zero day duration.

3.3.3.2 Schedule Constraints and Open Ended Logic

Constrain completion of the last activity in the schedule by the contract completion date. Schedule calculations shall result in a negative float when the calculated early finish date of the last activity is later than the contract completion date. Include as the last activity in the project schedule an activity called "End Project". The "End Project" activity shall have an "LF" constraint date equal to the contract completion date for the

SECTION 01 32 01.00 10 Page 7 project, and with a zero day duration or by using the "project must finish by" date in the scheduling software. The schedule shall have no constrained dates other than those specified in the contract. The use of artificial float constraints such as "zero fee float" or "zero total float" are typically prohibited. There shall only be 2 open ended activities: Start Project (or NTP) with no predecessor logic and End Project with no successor logic.

3.3.3.3 Early Project Completion

In the event the Preliminary or Initial project schedule calculates an early completion date of the last activity prior to the contract completion date, the Contractor shall identify those activities that it intends to accelerate and/or those activities that are scheduled in parallel to support the Contractor's "early" completion. The last activity shall have a late finish constraint equal to the contract completion date and the schedule will calculate positive float. The Government will not approve an early completion schedule with zero float on the longest path. The Government is under no obligation to accelerate activities for which it is responsible to support a proposed early contract completion.

3.3.4 Interim Completion Dates

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

3.3.4.1 Start Phase

Include as the first activity for a project phase an activity called "Start Phase X" where "X" refers to the phase of work. The "Start Phase X" activity shall have an "ES" constraint date equal to the date on which the NTP was acknowledged, and a zero day duration.

3.3.4.2 End Phase

Include as the last activity for a project phase an activity called "End Phase X" where "X" refers to the phase of work. The "End Phase X" activity shall have an "LF" constraint date equal to the specified completion date for that phase and a zero day duration.

3.3.4.3 Phase "X" Hammock

Include a hammock type activity for each project phase called "Phase X" where "X" refers to the phase of work. The "Phase X" hammock activity shall be logically tied to the earliest and latest activities in the phase.

3.3.5 Default Progress Data Disallowed

Do not automatically update Actual Start and Finish dates with default mechanisms that may be included in the scheduling software. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process shall match those dates provided from Contractor Quality Control Reports.

Failure of the Contractor to document the AS and AF dates on the Daily Quality Control report for every in-progress or completed activity, and

SECTION 01 32 01.00 10 Page 8 failure to ensure that the data contained on the Daily Quality Control reports is the sole basis for schedule updating shall result in the disapproval of the Contractor's updated schedule and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes.

Updating of the percent complete and the remaining duration of any activity shall be independent functions. Disable program features which calculate one of these parameters from the other.

3.3.6 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer. Propose logic corrections to eliminate all out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Correct out of sequence progress that continues for more than two update cycles by logic revision, as approved by the Contracting Officer.

3.3.7 Negative Lags and Start to Finish Relationships

Lag durations contained in the project schedule shall not have a negative value. Do not use Start to Finish (SF) relationships.

3.3.8 Calculation Mode

Schedule calculations shall retain the logic between predecessors and successors even when the successor activity starts and the predecessor activity has not finished. 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") will not be allowed.

3.3.9 Milestones

The schedule must include milestone activities for each significant project event including but not limited to: milestone activities for each fast track design package released for construction; design complete;

foundation/substructure construction complete; superstructure construction complete; building dry-in or enclosure complete to allow the initiation of finish activities; permanent power complete; and building systems commissioning complete.

3.4 PROJECT SCHEDULE SUBMISSIONS

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

SUBMISSION REQUIREMENTS.

3.4.1 Preliminary Project Schedule Submission

Submit the Preliminary Project Schedule, defining the Contractor's planned operations for the first 90 calendar days for approval within 15 calendar days after the NTP is acknowledged. 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

SECTION 01 32 01.00 10 Page 9 the contract award CLINS shown on the Price Schedule. Detail it for the first 90 calendar days. It may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as previously specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required Plan and Program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, the 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. Schedule any construction activities planned for the first 90 calendar days after NTP.

Constrain planned construction activities by Government acceptance of the associated design package(s) and all other specified Program and Plan approvals. Activity code any activities that are summary in nature after the first 90 calendar days with Responsibility Code (RESP) and Feature of Work code (FOW1, FOW2, FOW3).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after NTP. The schedule shall demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. The Initial Schedule shall be at a reasonable level of detail as determined by the Contracting Officer. Include in the 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.

3.4.3 Periodic Schedule Updates

Based on the result of the meeting, specified in PERIODIC SCHEDULE UPDATE MEETINGS, submit periodic schedule updates. These submissions will enable the Contracting Officer to assess Contractor's progress. If the Contractor fails or refuses to furnish the information and project schedule data, which in the judgement of the Contracting Officer 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.

3.4.4 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11, Appendix A. This exact structure is mandatory, even if some fields are not used. A template SDEF compatible schedule backup file (sdef.prx) is available on the QCS website: www.rmssupport.com.

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per Day 2 RESP 4 Responsible Party (e.g. GC, subcontractor, USACE)

SECTION 01 32 01.00 10 Page 10

3 AREA 4 Area of Work 4 MODF 6 Modification or REA number 5 BIDI 6 Bid Item (CLIN) 6 PHAS 2 Phase of Work 7 CATW 1 Category of Work 8 FOW1 10 Feature of Work (used up to 10 characters in length) 9 FOW2 10 Feature of Work (used up to 20 characters in length) 10 FOW3 10 Feature of Work (used up to 30 characters in length)

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's

Provide two sets of data CD's containing the project schedule in the backup format. Each CD shall also contain all previous update backup files. File medium shall be CD. Label each CD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule shall have a unique file name as determined by the Contractor.

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 shall include: a description of activities along the 2 most critical paths where the total float is less than or equal to 20 work days, 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. The narrative report is expected to communicate to the Government, the Contractor's thorough analysis of the schedule output and its plans to compensate for any problems, either current or potential, which are revealed through that analysis. Identify and explain why any activities that, based their calculated late dates, should have either started or finished during the update period but did not.

3.5.3 Approved Changes Verification

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

3.5.4 Schedule Reports

The format, filtering, organizing and sorting for each schedule report shall be as directed by the Contracting Officer. Typically reports shall 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

SECTION 01 32 01.00 10 Page 11

Complete. The following lists typical reports that will be requested. One or all of these reports may be requested for each schedule submission.

3.5.4.1 Activity Report

A list of all activities sorted according to activity number.

3.5.4.2 Logic Report

A 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 Contractor's Total Earnings on the project from the NTP to the data date. This report shall reflect the earnings of specific activities based on the agreements made in the schedule update meeting defined herein. Provided that the Contractor has furnished a complete schedule update, this report shall serve as the basis of determining progress payments. Group activities by CLIN item number and sort by activity number. This report shall: sum all activities coded to a particular CLIN and provide a CLIN item percent earned value; and complete and sum CLIN items to provide a total project percent complete. The printed report shall contain, for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Total Quantity, Quantity to Date, Percent Complete (based on cost), and Earnings to Date.

3.5.5 Network Diagram

The network diagram is required for the Preliminary, Initial and Periodic Updates. The network diagram shall depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.5.1 Continuous Flow

Diagrams shall 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 contract completion dates.

SECTION 01 32 01.00 10 Page 12

3.5.5.3 Critical Path

Clearly show the critical path.

3.5.5.4 Banding

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

3.5.5.5 S-Curves

Earnings curves showing projected early and late earnings and earnings to date.

3.6 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 requested by the Government. The meeting will last no longer than 8 hours. 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 the Authorized Representative of the Contracting Officer.

3.6.1 Update Submission Following Progress Meeting

Submit a complete update of the project schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 working days after the periodic schedule update meeting, reflecting only those changes made during the previous update meeting.

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

SECTION 01 32 01.00 10 Page 13

3.6.2.1 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 than 100% 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.2 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.3 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 contract 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.4 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 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 accurately sequencing the work.

3.6.2.5 Other Changes

Other changes required due to delays in completion of any activity or group of activities include: 1) delays beyond the Contractor's control, such as strikes and unusual weather. 2) delays encountered due to submittals, Government Activities, deliveries or work stoppages which make re-planning the work necessary. 3) Changes required to correct a schedule that does not represent the actual or planned prosecution and progress of the work.

3.7 REQUESTS FOR TIME EXTENSIONS

In the event the Contractor believes it is entitled to an extension of the contract performance period, completion date, or any interim milestone date, SECTION 01 32 01.00 10 Page 14 furnish the following for a determination by the Contracting Officer:

justification, project schedule data, and supporting evidence as the Contracting Officer may deem necessary. Submission of proof of excusable delay, based on revised activity logic, duration, and costs (updated to the specific date that the delay…