Attachment 2 - HAAW179035 Vol 1.pdf

PDF 4 MB Posted

Attached to
Squadron Operations Center Build / Upgrade Federal contract opportunity
Solicitation number
W50S8N20B0001
Issued by
Department of the Army National Guard

About this file

This is a solicitation for construction contracts for Projects HAAW179035 and HAAW162100 at Hancock Field Air National Guard Base in Syracuse, NY. The scope of work includes construction of a new 3,365 square foot addition to Building 643 and renovations and upgrades to the existing Squadron Operations Facility in Building 643. The North American Industry Classification System Code is 236220 and the size standard for small businesses is average annual revenue of $39.5M for the past three years. The project magnitude is between $1M and $5M. The pre-bid conference and site visit are highly encouraged. Bids must be submitted on all items or will be rejected. The solicitation, amendments and notices will be posted at SAM.gov. Instructions to obtain plans are in Section 00100. Funds are currently unavailable for CLIN 0003 but are expected to become available by 30 September 2020. This action has been identified on the National Guard priority list if funds become available and prices are within award range.

View the file

Other files for this federal contract opportunity

Other files attached to Squadron Operations Center Build / Upgrade, newest first.
File Type Posted
Bid Abstract.pdf PDF
Bid Opening Sign In.pdf PDF
Questions and Answers 29 May 2020.docx DOCX document
W50S8N20B00010004 Amendment.pdf PDF
Questions and Answers 27 May 2020.docx DOCX document
W50S8N20B00010004 Amendment.pdf PDF
W50S8N20B00010003 Amendment.pdf PDF
Questions and Answers 20 May 2020.docx DOCX document
HAAW179035-Addendum 02 - Dwg_R-A-601.pdf PDF
HAAW162100-Addendum 02 - Dwg_S-A-601.pdf PDF
W50S8N20B00010002 Amendment.pdf PDF
Questions and Answers 18 May 2020.docx DOCX document
Tax Form NY ST120_1_fill_in.pdf PDF
HAAW179035-Addendum 02 - Spec_08 14 00.pdf PDF
HAAW179035-Addendum 02 - Spec_23 11 25.pdf PDF
HAAW162100-Addendum 02 - Spec_08 14 00.pdf PDF
HAAW162100-Addendum 02 - Spec_09 29 00.pdf PDF
W50S8N20B00010001 Amendment.pdf PDF
HAAW179035-Addendum 02 - Spec_09 29 00.pdf PDF
W50S8N20B00010001 Amendment.pdf PDF
HAAW179035_Arch_ADDENDUM-001.pdf PDF
HAAW179035_Elec_Comm_ADDENDUM-001.pdf PDF
HAAW179035_Fire Alarm_ADDENDUM-001.pdf PDF
Pre-bid Slides HAAW179035-HAAW162100.pptx PPTX presentation
B643 Pre-Bid Sign In Sheet.pdf PDF
Attachment 7 - HAAW162100 Drawings.pdf PDF
Attachment 6 - HAAW179035 Drawings.pdf PDF
Attachment 3 - HAAW179035 Vol 2.pdf PDF
Attachment 1 - SOW HAAW179035_162100 25 Mar 2020.docx DOCX document
W50S8N20B0001 IFB Add_Alter B643.pdf PDF
Attachment 5 - HAAW162100 Vol 2.pdf PDF
Attachment 4 - HAAW162100 Vol 1.pdf PDF
Show all 32

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

New York

Air National Guard

Project No. HAAW179035

Construct Reaper Operations Center Building 643

174th Attack Wing Hancock Field Air National Guard Base

Syracuse, NY

Project Manual

Volume 1 of 2

December 2019

Type B-3 Submittal

Bidder’s Name and Address

CONSTRUCT REAPER OPERATIONS CENTER BUILDING 643

PROJECT NUMBER HAAW179035

174TH ATTACK WING

NEW YORK AIR NATIONAL GUARD

HANCOCK FIELD AIR NATIONAL GUARD BASE

SYRACUSE, NEW YORK

CERTIFICATION PAGE

SPECIFICATION INDEX

DOCUMENT / DIVISION

DESCRIPTION

DIVISION 01 GENERAL REQUIREMENTS

DIVISION 02

EXISTING CONDITIONS

DIVISION 03

DIVISION 04

DIVISION 05

DIVISION 06

CONCRETE

MASONRY

METALS

WOOD, PLASTICS, AND COMPOSITES

DIVISION 07

DIVISION 08

DIVISION 09

DIVISION 10

DIVISION 21

DIVISION 22

DIVISION 23

DIVISION 25

DIVISION 26

DIVISION 27

DIVISION 28

DIVISION 31

THERMAL AND MOISTURE PROTECTION

OPENINGS

FINISHES

SPECIALTIES

FIRE SUPPRESSION

PLUMBING

HEATING, VENTILATING, AND AIR

CONDITIONING (HVAC)

INTEGRATED AUTOMATION

ELECTRICAL

COMMUNICATIONS

ELECTRONIC SAFETY AND SECURITY

EARTHWORK

DIVISION 32

DIVISION 33

EXTERIOR IMPROVEMENTS

UTILITIES

CERTIFICATION(S)

12/9/2019

HAAW179035 Construct Reaper Operations Center Building 643 103179 Hancock Field Air National Guard Base, Syracuse, NY

PROJECT TABLE OF CONTENTS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 33 29 SUSTAINABILITY REPORTING

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 QUALITY CONTROL

01 45 35 SPECIAL INSPECTIONS

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

01 91 00.15 TOTAL BUILDING COMMISSIONING

DI VI SI ON 02 - EXI STI NG CONDI TI ONS

02 41 00 DEMOLITION

DI VI SI ON 03 - CONCRETE

03 30 00 CAST-IN-PLACE CONCRETE

03 45 00 PRECAST ARCHITECTURAL CONCRETE

DI VI SI ON 05 - METALS

05 12 00 STRUCTURAL STEEL

05 30 00 STEEL DECKS

05 40 00 COLD-FORMED METAL FRAMING

05 50 13 MISCELLANEOUS METAL FABRICATIONS

05 51 33 METAL LADDERS

DI VI SI ON 06 - WOOD, PLASTI CS, AND COMPOSI TES

06 10 00 ROUGH CARPENTRY

06 61 16 SOLID SURFACING FABRICATIONS

DI VI SI ON 07 - THERMAL AND MOI STURE PROTECTI ON

07 14 00 FLUID-APPLIED WATERPROOFING

07 21 13 BOARD AND BLOCK INSULATION

07 22 00 ROOF AND DECK INSULATION

07 27 10.00 10 BUILDING AIR BARRIER SYSTEM

07 27 19.01 SELF-ADHERING AIR BARRIERS

07 27 36 SPRAY FOAM AIR BARRIERS

07 42 63 FABRICATED WALL PANEL ASSEMBLIES

07 54 19 POLYVINYL-CHLORIDE ROOFING

07 60 00 FLASHING AND SHEET METAL

07 84 00 FIRESTOPPING

07 92 00.00 06 JOINT SEALANTS

07 95 00 EXPANSION CONTROL

DI VI SI ON 08 - OPENI NGS

PROJECT TABLE OF CONTENTS Page 1

08 11 13 STEEL DOORS AND FRAMES

08 34 73 SOUND CONTROL DOOR ASSEMBLIES

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

DI VI SI ON 09 - FI NI SHES

09 22 00 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 30 10 CERAMIC TILING

09 51 00 ACOUSTICAL CEILINGS

09 62 38 STATIC-CONTROL FLOORING

09 65 00 RESILIENT FLOORING

09 68 00 CARPETING

09 69 13 RIGID GRID ACCESS FLOORING

09 69 19 STRINGERLESS ACCESS FLOORING

09 90 00 PAINTS AND COATINGS

DI VI SI ON 10 - SPECI ALTI ES

10 11 00 VISUAL DISPLAY UNITS

10 14 00.10 EXTERIOR SIGNAGE

10 14 00.20 INTERIOR SIGNAGE

10 26 00 WALL AND DOOR PROTECTION

10 28 13 TOILET ACCESSORIES

DI VI SI ON 21 - FI RE SUPPRESSI ON

21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

DI VI SI ON 22 - PLUMBI NG

22 00 00 PLUMBING, GENERAL PURPOSE

DI VI SI ON 23 - HEATI NG, VENTI LATI NG, AND AI R CONDI TI ONI NG ( HVAC)

23 00 00 AIR SUPPLY, DISTRIBUTION, VENTILATION, AND EXHAUST SYSTEMS

23 03 00.00 20 BASIC MECHANICAL MATERIALS AND METHODS

23 05 15 COMMON PIPING FOR HVAC

23 05 48.00 40 VIBRATION AND SEISMIC CONTROLS FOR HVAC PIPING AND

EQUIPMENT

23 05 93 TESTING, ADJUSTING, AND BALANCING FOR HVAC

23 07 00 THERMAL INSULATION FOR MECHANICAL SYSTEMS

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC

23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC

23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS

23 23 00 REFRIGERANT PIPING

23 74 33.00 40 PACKAGED, OUTDOOR, HEATING AND COOLING MAKEUP

AIR-CONDITIONERS

23 81 00 DECENTRALIZED UNITARY HVAC EQUIPMENT

23 81 00.00 20 UNITARY AIR CONDITIONING EQUIPMENT

23 81 23.00 20 COMPUTER ROOM AIR CONDITIONING UNITS

DI VI SI ON 25 - I NTEGRATED AUTOMATI ON

25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END

AND INTEGRATION

PROJECT TABLE OF CONTENTS Page 2

DI VI SI ON 26 - ELECTRI CAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 05 48.00 10 SEISMIC PROTECTION FOR ELECTRICAL EQUIPMENT

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 29 23 VARIABLE FREQUENCY DRIVE SYSTEMS UNDER 600 VOLTS

26 41 00 LIGHTNING PROTECTION SYSTEM

26 51 00 INTERIOR LIGHTING

26 56 00 EXTERIOR LIGHTING

DI VI SI ON 27 - COMMUNI CATI ONS

27 05 28.36 40 CABLE TRAYS FOR COMMUNICATIONS SYSTEMS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

27 51 16 PUBLIC ADDRESS SYSTEMS

27 54 00.00 20 COMMUNITY ANTENNA TELEVISION (CATV) SYSTEMS

DI VI SI ON 28 - ELECTRONI C SAFETY AND SECURI TY

28 08 10 ELECTRONIC SECURITY SYSTEM ACCEPTANCE TESTING

28 10 05 ELECTRONIC SECURITY SYSTEMS (ESS)

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM

DI VI SI ON 31 - EARTHWORK

31 00 00 EARTHWORK

DI VI SI ON 32 - EXTERI OR I MPROVEMENTS

32 16 13 CONCRETE SIDEWALKS AND CURBS

32 92 19 SEEDING

DI VI SI ON 33 - UTI LI TI ES

33 30 00 SANITARY SEWERS

33 40 00 STORM DRAINAGE UTILITIES

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 3

THIS PAGE INTENTIONALLY LEFT BLANK

PROJECT TABLE OF CONTENTS Page 4

SECTION 01 11 00

SUMMARY OF WORK

08/15

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. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance with Section 01 33 29 SUSTAINABILITY REPORTING.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Utility Outage Requests

Utility Connection Requests

Excavation Permits

Welding Permits

Burning Permits

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The work includes the construction of a new 3,365 square foot, one-story addition to existing Building 643 to support the upgrades to the Reaper flight operations mission. The Project scope also includes associated Site Work and utilities to support the new addition. Renovations and upgrades to the existing Squadron Operations Facility will be accomplished under Project HAAW162100, Repair Squadron Operations Center Building 643.

1.2.2 Location

The work is located at Building 643, Hancock Field Air National Guard Base in Syracuse, NY, approximately as indicated. The exact location will be shown by the Contracting Officer.

1.3 OCCUPANCY OF PREMISES

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

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

1.4 EXISTING WORK

In addition to FAR 52.236-9 "Protection of Existing Vegetation, SECTION 01 11 00 Page 1

Structures, Equipment, Utilities, and Improvements":

a. Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work 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 Contracting Officer. At the completion of operations, existing work must be in a condition equal to or better than that which existed before new work started.

1.5 ON-SITE PERMITS

1.5.1 Borrow, Excavation, Welding, and Burning Permits

Coordinate all permit requirements with Contracting Officer.

Post permits at a conspicuous location in the construction area.

Burning of trash or rubbish is not permitted on Project Site.

1.6 LOCATION OF UNDERGROUND UTILITIES

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 Contract Drawings, within area of work.

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

1.6.1 Notification Prior to Excavation

Notify the Contracting Officer at least 48 hours prior to starting excavation work.

PART 2 PRODUCTS

Not Used.

PART 3 EXECUTION

Not Used.

-- End of Section --

SECTION 01 11 00 Page 2

SECTION 01 14 00

WORK RESTRICTIONS

11/11

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. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance with Section 01 33 29 SUSTAINABILITY REPORTING.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

The Contracting Officer will provide a list of required Preconstruction Submittals at the Preconstruction Conference.

1.2 SPECIAL SCHEDULING REQUIREMENTS

a. The facility will remain in operation during the entire construction period. The Contractor must conduct his operations so as to cause the least possible interference with normal operations of the activity.

b. Permission to interrupt any Activity roads, or utility service must be requested in writing a minimum of 30 calendar days prior to the desired date of interruption.

c. The work under this Contract requires special attention to the scheduling and conduct of the work in connection with existing operations. Identify on the Construction Schedule each factor which constitutes a potential interruption to operations.

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 Activity Regulations

Ensure that Contractor personnel employed on the Project become familiar with and obey base regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Ingress and egress of Contractor vehicles at the base is limited to the main base entry gate. Wear hard hats in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Mark Contractor equipment for identification.

1.3.1.1 Subcontractors and Personnel Contacts

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

1.3.1.2 Identification Badges and Installation Access

Application for and use of badges will be as directed by the Contracting Officer.

SECTION 01 14 00 Page 1

1.3.1.3 No Smoking Policy

Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.

1.3.2 Working Hours

Regular working hours must consist of a 9 hour period established by the Contracting Officer, between 7 a.m. and 4 p.m., Monday through Friday, excluding Government holidays.

1.3.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 7 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, Contract Number and Project Title. Based on the justification provided, the Contracting Officer may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer. Make utility cutovers after normal working hours or on Saturdays unless directed otherwise.

1.3.4 Occupied and Existing Building

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

Do not enter the building without prior approval of the Contracting Officer.

The existing buildings and their contents must be kept secure at all times. Provide temporary closures as required to maintain security as directed by the Contracting Officer.

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

The Government shall relocate movable furniture away from the Contractor's working area as required to perform the work, protect the furniture, and replace the furniture in its original location upon completion of the work.

Leave attached equipment in place, and protect it against damage, or temporarily disconnect, relocate, protect, and reinstall it at the completion of the work.

The Government will remove and relocate other Government property in the areas of the building scheduled to receive work.

1.3.5 Utility Cutovers and Interruptions

a. Make utility cutovers and interruptions after normal working hours or on Saturdays. Conform to procedures required Paragraph "Work Outside Regular Hours."

b. Ensure that new utility lines are complete, except for the connection, before interrupting existing service.

SECTION 01 14 00 Page 2

c. Interruption to water, sanitary sewer, storm sewer, telephone service, electric service, air conditioning, heating, fire alarm, and compressed air, are considered utility cutovers pursuant to the Paragraph "Work Outside Regular Hours."

PART 2 PRODUCTS

Not Used.

PART 3 EXECUTION

Not Used.

SECTION 01 14 00 Page 3

SECTION 01 14 00 Page 4

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

08/15

PART 1 GENERAL

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 SUBMITTALS

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

submittals not having a "G" designation are for Contractor Quality Control approval. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance with Section 01 33 29 SUSTAINABILITY REPORTING.

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, prior to or with the first digital photograph submittals, a sketch or drawing indicating the required photographic locations. Update as required if the locations are moved.

1.4 PROGRESS AND COMPLETION PICTURES

Photographically document Site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color minimum resolution in JPEG file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire Project from a minimum of ten views from points located by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures. Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file. Include a date designator in file names. Cross reference submittals in the appropriate daily report. Photographs provided are for unrestricted use by the Government.

SECTION 01 30 00 Page 1

1.5 MINIMUM INSURANCE REQUIREMENTS

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

1.6 SUPERVISION

1.6.1 Minimum Communication Requirements

Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the Job Site at all times during the performance of Contract Work. In addition, if a Quality Control (QC) representative is required on the Contract, then that individual must also have fluent English communication skills.

1.6.2 Superintendent Qualifications

The Project Superintendent must have a minimum of 10 years experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and Construction Drawings.

The qualification requirements for the Alternate Superintendent are the same as for the Project Superintendent. The Contracting Officer may request proof of the Superintendent's qualifications at any point in the Project if the performance of the Superintendent is in question.

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

1.6.2.1 Duties

The Project Superintendent is primarily responsible for managing and coordinating day-to-day production and schedule adherence on the Project.

The Superintendent or qualified alternative must be on-site at all times during the performance of this Contract until the work is completed and accepted.

1.6.3 Project Manager

Assign a Project Manager with the responsibility for the overall management of the Project. The Contracting Officer may request proof of the Project Manager's qualifications at any point in the Project if the performance of the Project Manager is in question.

1.6.3.1 Project Manager Qualifications

The Project Manager must have a minimum 10 years experience as a Project Manager or Superintendent on projects of similar size and complexity.

1.6.4 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the Contract and

SECTION 01 30 00 Page 2 for failure to manage the Project to insure timely completion.

Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.7 PRECONSTRUCTION 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 of prices or earned value report, Shop Drawings, and other submittals, scheduling programming, prosecution of the work, and clear expectations of the "Interim DD Form 1354" Submittal. Major Subcontractors who will engage in the work must also attend.

1.8 ELECTRONIC MAIL (E-MAIL) ADDRESS

Establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments as text files, pdf files, and other similar formats. Within 10 days after Contract Award, 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 e-mail to notify the Contractor of base access conditions when emergency conditions warrant, such as hurricanes or terrorist threats. Multiple e-mail addresses are not allowed.

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

PART 2 PRODUCTS

Not Used.

PART 3 EXECUTION

Not Used.

SECTION 01 30 00 Page 3

SECTION 01 30 00 Page 4

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (1995) Administration -- 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 approval. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance to Section 01 33 29 SUSTAINABILITY REPORTING.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Preliminary Project Schedule; G

Initial Project Schedule; G

Periodic Schedule Update; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

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

SECTION 01 32 01.00 10 Page 1

PART 2 PRODUCTS

2.1 SOFTWARE

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

2.1.1 Government Default Software

The Government intends to use Primavera P6.

2.1.2 Contractor Software

Scheduling software used by the Contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.

2.1.2.1 Primavera

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

2.1.2.2 Other Than Primavera

If the contractor chooses software other than Primavera P6, that is compliant with this Specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at Project Completion.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire Project is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Designers, Subcontractors and suppliers working on the Project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a Project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules. Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 BASIS FOR PAYMENT AND COST LOADING

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

SECTION 01 32 01.00 10 Page 2

3.2.1 Activity Cost Loading

Activity cost loading must be reasonable and without front-end loading.

Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this Specification may result in the disapproval of the preliminary, initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the Project Schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

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

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 work days or 30 calendar days.

3.3.3 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.3.4 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. Long procurement activities.

c. Submission and approval of O & M manuals.

d. Submission and approval of As-Built Drawings.

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

SECTION 01 32 01.00 10 Page 3

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

g. Submission of TAB specialist design review report.

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

i. Air and water balancing.

j. Building commissioning - Functional Performance Testing.

k. Controls testing plan submission.

l. Controls testing.

m. Other systems testing, if required.

n. Contractor's pre-final inspection.

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

p. Government's pre-final inspection.

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

r. Final inspection.

3.3.5 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, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.6 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

SECTION 01 32 01.00 10 Page 4

Field Activity Code Length Description

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

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

3.3.6.1 Workers Per Day (WRKP)

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

3.3.6.2 Responsible Party Coding (RESP)

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

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record); ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for Government).

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

SECTION 01 32 01.00 10 Page 5

3.3.6.4 Modification Number (MODF)

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

3.3.6.5 Bid Item Coding (BIDI)

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

3.3.6.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. If the Contract specifies phasing with separately defined performance periods, identify a Phase Code to allow filtering and organizing the schedule accordingly.

3.3.6.7 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to: Permits, construction submittal, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.

3.3.6.8 Feature of Work Coding (FOW)

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

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

3.3.7 Contract Milestones and Constraints

Milestone activities are to be used for significant Project events including, but not limited to, Project Phasing, Project Start and End Activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.

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

3.3.7.2 End Project Finish Milestone and Constraint

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

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

3.3.7.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.7.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.7.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.8 Calendars

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

If 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 Contract Clause "Time Extensions For Unusually Severe Weather." Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends .

3.3.9 Open Ended Logic

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

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

SECTION 01 32 01.00 10 Page 7

3.3.10 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.11 Out-of-Sequence Progress

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

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

3.3.12 Added and Deleted Activities

Do not delete activities from the Project Schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.

3.3.13 Original Durations

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

3.3.14 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.15 Retained Logic

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

3.3.16 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but

SECTION 01 32 01.00 10 Page 8 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.17 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.18 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.18.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.18.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.19 Early Completion Schedule and the Right to Finish Early

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

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

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

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are contained in Paragraph "Submission Requirements." If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, 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 Contract Documents.

SECTION 01 32 01.00 10 Page 9

3.4.1 Preliminary Project Schedule Submission

Within 15 calendar days after the NTP is acknowledged submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the Contract Award CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the Contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, permitting activities, and other non-construction activities intended to occur within the first 90 calendar days. 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.

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.

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 (e.g. .xer). 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.

SECTION 01 32 01.00 10 Page 10

3.5.2 Narrative Report

Provide a Narrative Report with each schedule submission. 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, lag changes, resource changes, and actual start and finish date changes.

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

3.5.3 Schedule Reports

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer. 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. The following lists typical reports that will be requested:

3.5.3.1 Activity Report

List of all activities sorted according to activity number.

3.5.3.2 Logic Report

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

3.5.3.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.3.4 Earnings Report by CLIN

A compilation of the Total Earnings on the Project from the NTP to the

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

3.5.3.5 Schedule Log

Provide a Scheduling/Leveling Report generated from the current Project Schedule being submitted.

3.5.4 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 Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.4.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.4.2 Project Milestone Dates

Show dates on the diagram for start of Project, any Contract required interim completion dates, and Contract Completion Dates.

3.5.4.3 Critical Path

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

3.5.4.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.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

With each schedule submission, provide a 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 purpose of reviewing the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and

SECTION 01 32 01.00 10 Page 12 progress payment. Conduct meetings at least monthly within five days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows all meeting participants to view the proposed schedule during the meeting. The Contractor's authorized scheduler must organize, group, sort, filter, perform schedule revisions as needed and review functions as requested by the Contractor and/or Government. The meeting is a working interactive exchange which allows the Government and Contractor the opportunity to review the updated schedule on a real time and interactive basis.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .