General Requirements.pdf

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

1.2 QUALIFICATIONS

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 BASIS FOR PAYMENT

3.3 PROJECT SCHEDULE

3.3.1 Use of the Critical Path Method

3.3.2 Level of Detail Required

3.3.2.1 Activity Durations

3.3.2.2 Procurement Activities

3.3.2.3 Critical Activities

3.3.2.4 Responsibility

3.3.2.5 Work Areas

3.3.2.6 Modification or Claim Number

3.3.2.7 Bid Item

3.3.2.8 Phase of Work

3.3.2.9 Feature of Work

3.3.3 Scheduled Project Completion

3.3.3.1 Project Start Date

3.3.3.2 Constraint of Last Activity

3.3.3.3 Early Project Completion

3.3.4 Interim Completion Dates

3.3.4.1 Start Phase

3.3.4.2 End Phase

3.3.4.3 Phase X

3.3.5 Default Progress Data Disallowed

3.3.6 Out-of-Sequence Progress

3.3.7 Negative Lags

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary Project Schedule Submission

3.4.2 Initial Project Schedule Submission

3.4.3 Periodic Schedule Updates

3.4.4 Standard Activity Coding Dictionary

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data Disks

3.5.1.1 File Medium

3.5.1.2 Disk Label

3.5.1.3 File Name

3.5.2 Narrative Report

01 32 01.00 10 -1

3.5.3 Approved Changes Verification

3.5.4 Schedule Reports

3.5.4.1 Activity Report

3.5.4.2 Logic Report

3.5.4.3 Total Float Report

3.5.4.4 Earnings Report

3.5.5 Network Diagram

3.5.5.1 Continuous Flow

3.5.5.2 Project Milestone Dates

3.5.5.3 Critical Path

3.5.5.4 Banding

3.5.5.5 S-Curves

3.6 PERIODIC PROGRESS MEETINGS

3.6.1 Meeting Attendance

3.6.2 Update Submission Following Progress Meeting

3.6.3 Progress Meeting Contents

3.6.3.1 Start and Finish Dates

3.6.3.2 Time Completion

3.6.3.3 Cost Completion

3.6.3.4 Logic Changes

3.6.3.5 Other Changes

3.7 REQUESTS FOR TIME EXTENSIONS

3.7.1 Justification of Delay

3.7.2 Submission Requirements

3.7.3 Additional Submission Requirements

3.8 DIRECTED CHANGES

3.9 OWNERSHIP OF FLOAT

-- End of Section Table of Contents --

01 32 01.00 10 -2

SECTION 01 32 01.00 10

PROJECT SCHEDULE

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)

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

1.2 QUALIFICATIONS

The Contractor shall designate an authorized representative who shall be responsible for the preparation of all required project schedule reports.

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS, a Project Schedule as described below shall be prepared. The scheduling of shall be the responsibility of the Contractor. Contractor management personnel shall actively participate in its development. working on the project shall also contribute in developing and maintaining an accurate Project Schedule. The approved Project Schedule shall be used to measure the progress of the work, to aid in evaluating time extensions, and to provide the basis of all progress payments.

3.2 BASIS FOR PAYMENT

The schedule shall be the basis for measuring Contractor progress. Lack of an approved schedule or scheduling personnel will result in an inability of the Contracting Officer to evaluate Contractor's progress for the purposes of payment. Failure of the Contractor to provide all information, as specified below, shall result in the disapproval of the entire Project Schedule submission and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes. In the case where Project Schedule revisions have been directed by the Contracting Officer and those revisions have not been included in the Project Schedule, the Contracting Officer may hold retainage up to the maximum allowed by contract, each payment period, until revisions to the Project Schedule have been made.

3.3 PROJECT SCHEDULE

The computer software system utilized by the Contractor to produce the

01 32 01.00 10 -3

Project Schedule shall be capable of providing all requirements of this specification. Failure of the Contractor to meet the requirements of this specification shall result in the disapproval of the schedule. Manual methods used to produce any required information shall require approval by the Contracting Officer.

3.3.1 Use of the Critical Path Method

The Critical Path Method (CPM) of network calculation shall be used to generate the Project Schedule. The Contractor shall provide the Project Schedule in the Precedence Diagram Method (PDM).

3.3.2 Level of Detail Required

The Project Schedule shall include an appropriate level of detail. Failure to develop or update the Project Schedule or provide data to the Contracting Officer at the appropriate level of detail, as specified by the Contracting Officer, shall result in the disapproval of the schedule. The Contracting Officer will use, but is not limited to, the following conditions to determine the appropriate level of detail to be used in the Project Schedule:

3.3.2.1 Activity Durations

Contractor submissions shall follow the direction of the Contracting Officer regarding reasonable activity durations. Reasonable durations are those that allow the progress of activities to be accurately determined between payment periods (usually less than 2 percent of all non-procurement activities' Original Durations are greater than 20 days).

3.3.2.2 Procurement Activities

Tasks related to the procurement of long lead materials or equipment shall be included as separate activities in the project schedule. Long lead materials and equipment are those materials that have a procurement cycle of over 90 days. Examples of procurement process activities include, but are not limited to: submittals, approvals, procurement, fabrication, and delivery.

3.3.2.3 Critical Activities

The following activities shall be listed as separate line activities on the Contractor's project schedule:

a. Submission and approval of mechanical/electrical layout drawings.

b. Submission and approval of O & M manuals.

c. Submission and approval of as-built drawings.

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

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

f. Submission of TAB specialist design review report.

g. Submission and approval of fire protection specialist.

h. Submission and approval of testing and balancing of HVAC plus

01 32 01.00 10 -4 commissioning plans and data.

i. Air and water balance dates.

j. HVAC commissioning dates.

k. Controls testing plan.

l. Controls testing.

m. Performance Verification testing.

n. Other systems testing, if required.

o. Prefinal inspection.

p. Correction of punchlist from prefinal inspection.

q. Final inspection.

3.3.2.4 Responsibility

All activities shall be identified in the project schedule by the party responsible to perform the work. Responsibility includes, but is not limited to, the subcontracting firm, contractor work force, or government agency performing a given task. Activities shall not belong to more than one responsible party. The responsible party for each activity shall be identified by the Responsibility Code.

3.3.2.5 Work Areas

All activities shall be identified in the project schedule by the work area in which the activity occurs. Activities shall not be allowed to cover more than one work area. The work area of each activity shall be identified by the Work Area Code.

3.3.2.6 Modification or Claim Number

Any activity that is added or changed by contract modification or used to justify claimed time shall be identified by a mod or claim code that changed the activity. Activities shall not belong to more than one modification or claim item. The modification or claim number of each activity shall be identified by the Mod or Claim Number. Whenever possible, changes shall be added to the schedule by adding new activities.

Existing activities shall not normally be changed to reflect modifications.

3.3.2.7 Bid Item

All activities shall be identified in the project schedule by the Bid Item to which the activity belongs. An activity shall not contain work in more than one bid item. The bid item for each appropriate activity shall be identified by the Bid Item Code.

3.3.2.8 Phase of Work

All activities shall be identified in the project schedule by the phases of work in which the activity occurs. Activities shall not contain work in more than one phase of work. The project phase of each activity shall be by the unique Phase of Work Code.

01 32 01.00 10 -5

3.3.2.9 Feature of Work

All activities shall be identified in the project schedule according to the feature of work to which the activity belongs. Feature of work refers, but is not limited to, a work breakdown structure for the project. The feature of work for each activity shall be identified by the Feature of Work Code.

3.3.3 Scheduled Project Completion

The schedule interval shall extend from NTP to the contract completion date.

3.3.3.1 Project Start Date

The schedule shall start no earlier than the date on which the NTP was acknowledged. The Contractor shall include as the first activity in the project schedule an activity called "Start Project". 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 Constraint of Last Activity

Completion of the last activity in the schedule shall be constrained by the contract completion date. Calculation on project updates shall be such that if the early finish of the last activity falls after the contract completion date, then the float calculation shall reflect a negative float on the critical path. The Contractor shall 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 completion date for the project, and a zero day duration.

3.3.3.3 Early Project Completion

In the event the project schedule shows completion of the project prior to the contract completion date, the Contractor shall identify those activities that have been accelerated and/or those activities that are scheduled in parallel to support the Contractor's "early" completion.

Contractor shall specifically address each of the activities noted in the narrative report at every project schedule update period to assist the Contracting Officer in evaluating the Contractor's ability to actually complete prior to the contract period.

3.3.4 Interim Completion Dates

Contractually specified interim completion dates shall also be constrained to show negative float if the early finish date of the last activity in that phase falls after the interim completion date.

3.3.4.1 Start Phase

The Contractor shall 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

The Contractor shall include as the last activity in a project phase an activity called "End Phase X" where "X" refers to the phase of work. The

01 32 01.00 10 -6

"End Phase X" activity shall have an "LF" constraint date equal to the completion date for the project, and a zero day duration.

3.3.4.3 Phase X

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

3.3.5 Default Progress Data Disallowed

Actual Start and Finish dates shall not be automatically updated by default mechanisms that may be included in CPM scheduling software systems. Actual Start and Finish dates on the CPM schedule shall match those dates provided from Contractor Quality Control Reports. Failure of the Contractor to document the Actual Start and Finish dates on the Daily Quality Control report for every in-progress or completed activity, and 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 schedule and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes.

3.3.6 Out-of-Sequence Progress

Activities that have posted progress without all preceding logic being satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case approval of the Contracting Officer. The Contractor shall 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.

3.3.7 Negative Lags

Lag durations contained in the project schedule shall not have a negative value.

3.4 PROJECT SCHEDULE SUBMISSIONS

The Contractor shall provide the submissions as described below. The data disk, reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS.

3.4.1 Preliminary Project Schedule Submission

The Preliminary Project Schedule, defining the Contractor's planned operations for the first 60 calendar days shall be submitted for approval within 20 calendar days after the NTP is acknowledged. The approved preliminary schedule shall be used for payment purposes not to exceed 60 calendar days after NTP.

3.4.2 Initial Project Schedule Submission

The Initial Project Schedule shall be submitted for approval within 40 calendar days after NTP. The schedule shall provide a reasonable sequence of activities which represent work through the entire project and shall be at a reasonable level of detail.

01 32 01.00 10 -7

3.4.3 Periodic Schedule Updates

Based on the result of progress meetings, specified in "Periodic Progress Meetings," the Contractor shall submit periodic schedule updates. These submissions shall 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 judgment 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

The Contractor shall 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.

3.5 SUBMISSION REQUIREMENTS

The following items shall be submitted by the Contractor for the preliminary submission, initial submission, and every periodic project schedule update throughout the life of the project:

3.5.1 Data Disks

Two data disks containing the project schedule shall be provided. Data on the disks shall adhere to the SDEF format specified in ER 1-1-11, Appendix A.

3.5.1.1 File Medium

Required data shall be submitted on 3.5 disks, formatted to hold 1.44 MB of data, under the MS-DOS Version 5. or 6.x, unless otherwise approved by the Contracting Officer.

3.5.1.2 Disk Label

A permanent exterior label shall be affixed to each disk submitted. The label shall indicate the type of schedule (Preliminary, Initial, Update, or Change), full contract number, project name, project location, data date, name and telephone number of person responsible for the schedule, and the MS-DOS version used to format the disk.

3.5.1.3 File Name

Each file submitted shall have a name related to either the schedule data date, project name, or contract number. The Contractor shall develop a naming convention that will ensure that the names of the files submitted are unique. The Contractor shall submit the file naming convention to the Contracting Officer for approval.

3.5.2 Narrative Report

A Narrative Report shall be provided with the preliminary, initial, and each update of the project schedule. This report shall be provided as the basis of the Contractor's progress payment request. The Narrative Report shall include: a description of activities along the 2 most critical paths, a description of current and anticipated problem areas or delaying factors and their impact, and an explanation of corrective actions taken or

01 32 01.00 10 -8 required to be taken. The narrative report is expected to relay 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.

3.5.3 Approved Changes Verification

Only project schedule changes that have been previously approved by the Contracting Officer shall be included in the schedule submission. 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 for each activity for the schedule reports listed below 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 and Actual Finish Dates shall be printed for those activities in progress or completed.

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 Preceding and Succeeding activities for every activity in ascending order by activity number. Preceeding and succeeding activities shall include all information listed above in paragraph Schedule Reports.

A blank line shall be left between each activity grouping.

3.5.4.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. Activities which have the same amount of total float shall be listed in ascending order of Early Start Dates. Completed activities shall not be shown on this report.

3.5.4.4 Earnings Report

A compilation of the Contractor's Total Earnings on the project from the NTP until the most recent Monthly Progress Meeting. This report shall reflect the Earnings of specific activities based on the agreements made in the field and approved between the Contractor and Contracting Officer at the most recent Monthly Progress Meeting. Provided that the Contractor has provided a complete schedule update, this report shall serve as the basis of determining Contractor Payment. Activities shall be grouped by bid item and sorted by activity numbers. This report shall: sum all activities in a bid item and provide a bid item percent; and complete and sum all bid 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 shall be required on the initial schedule submission and on monthly schedule update submissions. The network diagram shall

01 32 01.00 10 -9 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. The activity number, description, duration, and estimated earned value shall be shown on the diagram.

3.5.5.2 Project Milestone Dates

Dates shall be shown on the diagram for start of project, any contract required interim completion dates, and contract completion dates.

3.5.5.3 Critical Path

The critical path shall be clearly shown.

3.5.5.4 Banding

Activities shall be grouped 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 PROGRESS MEETINGS

Progress meetings to discuss payment shall include a monthly onsite meeting or other regular intervals mutually agreed to at the preconstruction conference. During this meeting the Contractor shall describe, on an activity by activity basis, all proposed revisions and adjustments to the project schedule required to reflect the current status of the project.

The Contracting Officer will approve activity progress, proposed revisions, and adjustments as appropriate.

3.6.1 Meeting Attendance

The Contractor's Project Manager and Scheduler shall attend the regular progress meeting.

3.6.2 Update Submission Following Progress Meeting

A complete update of the project schedule containing all approved progress, revisions, and adjustments, based on the regular progress meeting, shall be submitted not later than 4 working days after the monthly progress meeting.

3.6.3 Progress Meeting Contents

Update information, including Actual Start Dates, Actual Finish Dates, Remaining Durations, and Cost-to-Date shall be subject to the approval of the Contracting Officer. As a minimum, the Contractor shall address the following items on an activity by activity basis during each progress meeting.

01 32 01.00 10 -10

3.6.3.1 Start and Finish Dates

The Actual Start and Actual Finish dates for each activity currently in-progress or completed.

3.6.3.2 Time Completion

The estimated Remaining Duration for each activity in-progress. Time-based progress calculations shall be based on Remaining Duration for each activity.

3.6.3.3 Cost Completion

The earnings for each activity started. Payment will be based on earnings for each in-progress or completed activity. Payment for individual activities will not be made for work that contains quality defects. A portion of the overall project amount may be retained based on delays of activities.

3.6.3.4 Logic Changes

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, lag durations, and other changes that have been made pursuant to contract provisions shall be specifically identified and discussed.

3.6.3.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 which does not represent the actual or planned prosecution and progress of the work.

3.7 REQUESTS FOR TIME EXTENSIONS

In the event the Contractor requests an extension of the contract completion date, or any interim milestone date, the Contractor shall furnish the following for a determination as to whether or not the Contractor is entitled to an extension of time under the provisions of the contract: justification, project schedule data, and supporting evidence as the Contracting Officer may deem necessary. Submission of proof of delay, based on revised activity logic, duration, and costs (updated to the specific date that the delay occurred) is obligatory to any approvals.

3.7.1 Justification of Delay

The project schedule shall clearly display that the Contractor has used, in full, all the float time available for the work involved with this request. The Contracting Officer's determination as to the number of allowable days of contract extension shall be based upon the project schedule updates in effect for the time period in question, and other factual information. Actual delays that are found to be caused by the Contractor's own actions, which result in the extension of the schedule, will not be a cause for a time extension to the contract completion date.

01 32 01.00 10 -11

3.7.2 Submission Requirements

The Contractor shall submit a justification for each request for a change in the contract completion date of under 2 weeks based upon the most recent schedule update at the time of the NTP or constructive direction issued for the change. Such a request shall be in accordance with the requirements of other appropriate Contract Clauses and shall include, as a minimum:

a. A list of affected activities, with their associated project schedule activity number.

b. A brief explanation of the causes of the change.

c. An analysis of the overall impact of the changes proposed.

d. A sub-network of the affected area.

Activities impacted in each justification for change shall be identified by a unique activity code contained in the required data file.

3.7.3 Additional Submission Requirements

For any requested time extension of over 2 weeks, the Contracting Officer may request an interim update with revised activities for a specific change request. The Contractor shall provide this disk within 4 days of the Contracting Officer's request.

3.8 DIRECTED CHANGES

If the NTP is issued for changes prior to settlement of price and/or time, the Contractor shall submit proposed schedule revisions to the Contracting Officer within 2 weeks of the NTP being issued. The proposed revisions to the schedule will be approved by the Contracting Officer prior to inclusion of those changes within the project schedule. If the Contractor fails to submit the proposed revisions, the Contracting Officer may furnish the Contractor with suggested revisions to the project schedule. The Contractor shall include these revisions in the project schedule until revisions are submitted, and final changes and impacts have been negotiated. If the Contractor has any objections to the revisions furnished by the Contracting Officer, the Contractor shall advise the Contracting Officer within 2 weeks of receipt of the revisions. Regardless of the objections, the Contractor shall continue to update the schedule with the Contracting Officer's revisions until a mutual agreement in the revisions is reached. If the Contractor fails to submit alternative revisions within 2 weeks of receipt of the Contracting Officer's proposed revisions, the Contractor will be deemed to have concurred with the Contracting Officer's proposed revisions. The proposed revisions will then be the basis for an equitable adjustment for performance of the work.

3.9 OWNERSHIP OF FLOAT

Float available in the schedule, at any time, shall not be considered for the exclusive use of either the Government or the Contractor.

-- End of Section --

01 32 01.00 10 -12

SECTION 01 33 00

SUBMITTAL PROCEDURES

PART 1 GENERAL

1.1 DEFINITIONS

1.1.1 Submittal

1.1.2 Submittal Descriptions (SD)

1.1.3 Approving Authority

1.1.4 Work

1.2 SUBMITTALS

1.3 SUBMITTAL CLASSIFICATION

1.3.1 Information Only

1.4 APPROVED SUBMITTALS

1.5 DISAPPROVED SUBMITTALS

1.6 GENERAL

1.7 SCHEDULING

1.8 TRANSMITTAL FORM (ENG FORM 4025)

1.9 SUBMITTAL PROCEDURES

1.9.1 Procedures

1.9.2 Deviations

1.10 CONTROL OF SUBMITTALS

1.11 GOVERNMENT APPROVED SUBMITTALS

1.12 INFORMATION ONLY SUBMITTALS

1.13 STAMPS

01 33 00 -1

SECTION 01 33 00

SUBMITTAL PROCEDURES

PART 1 GENERAL

1.1 DEFINITIONS

1.1.1 Submittal

Contract Clauses "FAR 52.236-5, Material and Workmanship," paragraph (b) and "FAR 52.236-21, Specifications and Drawings for Construction," paragraphs (d), (e), and (f) apply to all "submittals."

Submittals are listed in 01012 2.1

1.1.2 Submittal Descriptions (SD)

Submittals requirements are specified in the technical sections.

Submittals are identified by SD numbers and titles as follows.

SD-01 Preconstruction Submittals

Certificates of insurance.

Surety bonds.

List of proposed subcontractors.

List of proposed products.

Construction Progress Schedule.

Submittal register.

Schedule of prices.

Health and safety plan.

Work plan.

Quality control plan.

Environmental protection plan.

SD-02 Shop Drawings

Drawings, diagrams and schedules specifically prepared to illustrate some portion of the work.

Diagrams and instructions from a manufacturer or fabricator for use in producing the product and as aids to the Contractor for integrating the product or system into the project.

Drawings prepared by or for the Contractor to show how multiple systems and interdisciplinary work will be coordinated.

SD-03 Product Data

Catalog cuts, illustrations, schedules, diagrams, performance charts, instructions and brochures illustrating size, physical appearance and other characteristics of materials or equipment for some portion of the work.

Samples of warranty language when the contract requires extended

01 33 00 -2 product warranties.

SD-04 Samples

Physical examples of materials, equipment or workmanship that illustrate functional and aesthetic characteristics of a material or product and establish standards by which the work can be judged.

Color samples from the manufacturer's standard line (or custom color samples if specified) to be used in selecting or approving colors for the project.

Field samples and mock-ups constructed on the project site establish standards by which the ensuring work can be judged. Includes assemblies or portions of assemblies which are to be incorporated into the project and those which will be removed at conclusion of the work.

SD-05 Design Data

Calculations, mix designs, analyses or other data pertaining to a part of work.

SD-06 Test Reports

Report signed by authorized official of testing laboratory that a material, product or system identical to the material, product or system to be provided has been tested in accord with specified requirements. (Testing must have been within three years of date of contract award for the project.)

Report which includes findings of a test required to be performed by the Contractor on an actual portion of the work or prototype prepared for the project before shipment to job site.

Report which includes finding of a test made at the job site or on sample taken from the job site, on portion of work during or after installation.

Investigation reports.

Daily checklists.

Final acceptance test and operational test procedure.

SD-07 Certificates

Statements printed on the manufacturer's letterhead and signed by responsible officials of manufacturer of product, system or material attesting that product, system or material meets specification requirements. Must be dated after award of project contract and clearly name the project.

Document required of Contractor, or of a supplier, installer or subcontractor through Contractor, the purpose of which is to further quality of orderly progression of a portion of the work by documenting procedures, acceptability of methods or personnel qualifications.

Confined space entry permits.

01 33 00 -3

Text of posted operating instructions.

SD-08 Manufacturer's Instructions

Preprinted material describing installation of a product, system or material, including special notices and Material Safety Data sheets concerning impedances, hazards and safety precautions.

SD-09 Manufacturer's Field Reports

Documentation of the testing and verification actions taken by manufacturer's representative to confirm compliance with manufacturer's standards or instructions.

Factory test reports.

SD-10 Operation and Maintenance Data

Data that is furnished by the manufacturer, or the system provider, to the equipment operating and maintenance personnel. This data is needed by operating and maintenance personnel for the safe and efficient operation, maintenance and repair of the item.

SD-11 Closeout Submittals

Documentation to record compliance with technical or administrative requirements or to establish an administrative mechanism.

1.1.3 Approving Authority

Office authorized to approve submittal.

1.1.4 Work

As used in this section, on- and off-site construction required by contract documents, including labor necessary to produce submittals, construction, materials, products, equipment, and systems incorporated or to be incorporated in such construction.

1.2 SUBMITTALS

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

submittals not having a "G" designation are for information only or as otherwise designated. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. The following shall be submitted in accordance with Section

01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Submittal register; G

1.3 SUBMITTAL CLASSIFICATION

Submittals are classified as follows:

01 33 00 -4

1.3.1 Information Only

They are not considered to be "shop drawings" within the terms of the Contract Clause referred to above.

All submittals not requiring Government approval will be for information only. They are not considered to be "shop drawings" within the terms of the Contract Clause referred to above.

1.4 APPROVED SUBMITTALS

The Contracting Officer's approval of submittals shall not be construed as a complete check, but will indicate only that . Approval will not relieve the Contractor of the responsibility for any error which may exist, as the Contractor under the Contractor Quality Control (CQC) requirements of this contract is responsible for design, dimensions, all design extensions, such as the design of adequate connections and details, etc., and the satisfactory construction of all work. After submittals have been approved by the Contracting Officer, no resubmittal for the purpose of substituting materials or equipment will be considered unless accompanied by an explanation of why a substitution is necessary.

1.5 DISAPPROVED SUBMITTALS

If the Contractor considers any correction indicated on the submittals to constitute a change to the contract, a notice in accordance with the Contract Clause "Changes" shall be given promptly to the Contracting Officer.

1.6 GENERAL

The Contractor shall make submittals as required by the specifications.

The Contracting Officer may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections. Units of weights and measures used on all submittals shall be the same as those used in the contract drawings. Each submittal shall be complete and in sufficient detail to allow ready determination of compliance with contract requirements. Prior to submittal, all items shall be checked and approved by the Contractor's and each item shall be stamped, signed, and dated by the CQC System Manager indicating action taken. Proposed deviations from the contract requirements shall be clearly identified. Submittals shall include items such as:

Contractor's, manufacturer's, or fabricator's drawings; descriptive literature including (but not limited to) catalog cuts, diagrams, operating charts or curves; test reports; test cylinders; samples; O&M manuals (including parts list); certifications; warranties; and other such required submittals. Submittals requiring Government approval shall be scheduled and made prior to the acquisition of the material or equipment covered thereby. Samples remaining upon completion of the work shall be picked up and disposed of in accordance with manufacturer's Material Safety Data Sheets (MSDS) and in compliance with existing laws and regulations.

1.7 SCHEDULING

Submittals covering component items forming a system or items that are interrelated shall be scheduled to be coordinated and submitted concurrently. Certifications to be submitted with the pertinent drawings shall be so scheduled. Adequate time (a minimum of thirty-five calendar days exclusive of mailing time) shall be allowed and shown on the register

01 33 00 -5 for review and approval. No delay damages or time extensions will be allowed for time lost in late submittals.

1.8 TRANSMITTAL FORM (ENG FORM 4025)

The sample transmittal form (ENG Form 4025) attached to this RFP shall be used for submitting both Government approved and information only submittals in accordance with the instructions on the reverse side of the form. These forms are included in the QCS software that the Contractor is required to use for this contract. This form shall be properly completed by filling out all the heading blank spaces and identifying each item submitted. Special care shall be exercised to ensure proper listing of the specification paragraph and/or sheet number of the contract drawings pertinent to the data submitted for each item.

1.9 SUBMITTAL PROCEDURES

Submittals shall be made as follows:

1.9.1 Procedures

1.9.2 Deviations

For submittals which include proposed deviations requested by the Contractor, the column "variation" of ENG Form 4025 shall be checked. The Contractor shall set forth in writing the reason for any deviations and annotate such deviations on the submittal. The Government reserves the right to rescind inadvertent approval of submittals containing unnoted deviations.

1.10 CONTROL OF SUBMITTALS

The Contractor shall carefully control his procurement operations to ensure that each individual submittal is made on or before the Contractor scheduled submittal date shown on the approved "Submittal Register."

1.11 GOVERNMENT APPROVED SUBMITTALS

Upon completion of review of submittals requiring Government approval, the submittals will be identified as having received approval by being so stamped and dated. Four copies of the submittal will be retained by the Contracting Officer and two copies of the submittal will be returned to the Contractor and one additional copy to user On-site representative.

1.12 INFORMATION ONLY SUBMITTALS

Normally submittals for information only will not be returned. Approval of the Contracting Officer is not required on information only submittals.

The Government reserves the right to require the Contractor to resubmit any item found not to comply with the contract. This does not relieve the Contractor from the obligation to furnish material conforming to the plans and specifications; will not prevent the Contracting Officer from requiring removal and replacement of nonconforming material incorporated in the work;

and does not relieve the Contractor of the requirement to furnish samples for testing by the Government laboratory or for check testing by the Government in those instances where the technical specifications so prescribe.

01 33 00 -6

1.13 STAMPS

Stamps used by the Contractor on the submittal data to certify that the submittal meets contract requirements shall be similar to the following:

01 33 00 -7

| CONTRACTOR |

| (Firm Name) | | _____ Approved | | _____ Approved with corrections as noted on submittal data and/or | | attached sheets(s). |

| SIGNATURE: __________________________________________________________ |

| TITLE: ______________________________________________________________ |

| DATE: _______________________________________________________________ |

-- End of Section --

01 33 00 -8

01 33 16 ‐1

SECTION 01 33 16

DESIGN AFTER AWARD

December 18, 2008 Revised; June10, 2010*

1 SUBMISSION OF CONSTRUCTION DRAWINGS, SPECIFICATIONS AND DESIGN

ANALYSES:

The contractor shall follow the design submission requirements as listed below. In addition, the contractor shall comply with other design submission requirements as listed and required in other areas of the RFP.

1.1 The following web addresses contain guides and criteria necessary to support completion of the project design. See Section 01 10 10 for other guides and criteria required for the design and construction of the project.

1.1.1 General Guidance: General guidance is listed on the Criteria Bulletin Board System (CBBS) page for A-E Firms and Basic Design Package http://cbbs.spk.usace.army.mil/ae.html. A description of submittal content can be found by selecting AE Guide Volume 1, General Instructions for Air Force projects -http://cbbs.spk.usace.army.mil/PDF/aeguide/index.html -- Chapter III.

1.1.2 CADD Standards: The Sacramento District CADD Standards are provided on the CBBS page http://www.spk.usace.army.mil/organizations/cespk-ed/SPKCADD/index.html. The A/E/C CADD Standard developed by The CADD/GIS Technology Center is available at https://tsc.wes.army.mil/

1.1.3 Design Analysis and Drawings Baseline Guidance ER 1110-345-700 (serves as a baseline guide and may be adjusted if/as noted herein):

http://www.usace.army.mil/inet/usace-docs/eng-regs/er1110-345-700/toc.html

1.1.4 Specifications Baseline Guidance ER 1110-1-8155, Engineer and Design – Specifications:

http://www.usace.army.mil/publications/eng-regs/er1110-1-8155/entire.pdfl

1.1.5 Air Force Civil Engineering Sustainability Policy (use of LEEDs):

http://www.afcee.brooks.af.mil/dc/dcd/arch/rfg/index.html. Also see http://www.afcee.brooks.af.mil/eq/programs/progpage.asp?PID=27 and http://cbbs.spk.usace.army.mil/sustain.html.

1.1.6 Unified Facilities Guide Specifications (UFGS) Listing (UFGS is the required format for the design guide specs): http://www.wbdg.org/ccb/. Use the JANUARY 2006 MasterFormat 95 SPECSINTACT DATABASE for this project.

1.1.7 Unified Facilities Criteria (UFC): http://www.wbdg.org/ccb/browse.

1.1.8 Air Force Engineering Technical Letters (ETLs): for newer ETLs go to http://www.afcesa.af.mil/library/etl.asp?Category=Engineering%20Technical%20Letters

01 33 16 ‐2

, for a complete listing go to http://www.wbdg.org/ccb/browse_cat.php?o=33&c=125, for older ETLs go to http://cbbs.spk.usace.army.mil/afetl.html

1.1.9 Air Force Publications: http://www.e-publishing.af.mil/

1.1.10 Overall Design Site: The CBBS site will offer a pathway to regularly used criteria: http://cbbs.spk.usace.army.mil/index.html

1.1.11 Air Force Interior Design Guide and other products and services offered by AFCEE: This site includes the guidance and specifications to be followed during the development and design of the Air Force structural interior design and the comprehensive interior design (UFC 3 120 10: Interior Design):

http://www.wbdg.org/ccb/DOD/UFC/ufc_3_120_10.pdf

This site includes additional information for other products and services:

http://www.afcee.af.mil/resources/designandconstruction/familyhousingpublications/index.as p

2 Submittal certifications:

2.1 The Contractor shall certify in the design submittal (by cover letter) that all items submitted in the documents comply with the contract. This shall be provided for each track’s submittals through and including final design submittal. Attached to this letter shall be the signed certifications from each of the independent technical reviewers.

2.2 The content of each independent technical reviewer certification shall include the following statement on his/her company’s letterhead:

2.2.1 I (name of reviewer with title(s)) have completed the independent technical review for (stage of submittal) of (project name and location) design submittal. Notice is hereby given that all quality control activities, appropriate to the level of risk and complexity inherent in the project, as defined in the Quality Control Plan have been completed. Compliance with the contract, established policy principles and procedures, utilizing justified and valid assumptions, was verified. This included review of assumptions; methods, procedures, and material used in analyses; alternatives evaluated; the appropriateness of data used and level of data obtained; and reasonableness of the results, including whether the product meets the customer's needs consistent with law and existing Air Force and Corps of Engineers policy.

Documentation of the quality control process is attached. Significant concerns and the explanation of their resolution are as follows: (Describe the major technical concerns, possible impact, and resolution)

2.3 The “For Construction” submittal for the project, building, and/or site system shall be accompanied with a letter from each key sub-contractor/ supplier having direct construction/materials/ equipment defined within the submittal. The purpose of the letter is to bring together and coordinate the designers and the sub-contractors slated to accomplish the work and the suppliers of the material and equipment. Each

01 33 16 ‐3 sub-contractor and supplier shall briefly state their involvement in the preparation of the submittal, their proposed activity during the design-build contract associated with the contents of the submittal, and state the design is appropriate for their related field and appropriate for their capabilities/expertise. Each letter shall be on the sub-contractor’s/supplier’s letter head and signed by a principal of the firm. Included with these letters shall be the certifications from each of the independent technical reviewers. In addition --- each drawing shall be stamped and signed by the responsible designer and the responsible licensed professional technical reviewer (two signed stamps required on each drawing).

3 Criteria and Deviations

3.1 The criteria specified in this Contract are binding contract criteria and in case of any conflict, after award, between the Contract and Contractor's submittals, the Contract will govern unless there is a written and signed agreement between the Contracting Officer and the Contractor modifying a specific requirement.

3.2 Contractor’s deviations from the Contract requirements (shall be defined in a letter submitted to the Contracting Officer with justification, analysis, and detailed cost savings and shall also be presented and highlighted in a separate section in the analysis so it is clear to the reviewer) may be considered by the Government, and where appropriate, may be specifically approved by the Contracting Officer. Deviations from the contract requirements shall not be assumed or considered approved unless contractually approved by the Contracting Officer in writing. Such deviations, when not contractually approved by the Contracting Officer or when subsequently found at any time during the contract, shall be corrected by the Contractor at no additional time or cost to the Government. It is the Contractor’s responsibility to clearly note features/aspects in his design or construction that are deviations to the contract requirements. The Contractor shall not assume silence on such issues by the Government to be a sign of acceptance. The Contractor is cautioned to not work verbally approved adjustments to the contract but rather to work adjustments to the contract in writing with Government personnel having appropriate authority to execute such adjustments to the contract.

4 Topographic and Geotechnical Considerations

4.1 The Contractor shall verify and determine field conditions, by field inspection, field exploration, and other means deemed appropriate and necessary for proposal, design, and construction to yield a safe, complete, and useable facility/supporting features for their intended use. The information shall be reflected in the design documents.

4.2 The Contractor is required to conduct all topographic surveys and necessary related activity in accordance with the information contained herein and as appropriate/applicable from the Base Design Standards. The reviewed and corrected (as appropriate) topographic survey shall be the basis for design of the topographic

01 33 16 ‐4 features and controls for all projects. This survey shall include all areas necessary to design and build all features required in base pricing schedule and option pricing schedule items. All Projects with data as a deliverable, will be delivered in Universal Transverse Mercator (UTM 12 North) coordinate system, World Geodetic System 1984 WGS84) datum and use metric coordinate units. The North American Vertical Datum of 1988 (NAVD88) will be used as a basis for all elevations. As a part of each design submittal, the contractor/designer shall include the following information that will be imported into the Hill AFB GIS platform;

4.2.1 Ground elevation and simple building envelope massing (i.e.: entry canopy, equipment, etc.).

4.2.2 Elevation of each floor and/or Mezzanine.

4.2.3 Elevation of the roof plane, parapet, and all projecting objects (stacks/mechanical equipment above the roof plane, etc.)

4.2.4 Object envelope simple massing for all ground mounted equipment (i.e.

transformers, chillers, compactors, compressors, bag filters, etc.).

4.3 The Contractor is required to conduct all geotechnical and foundation site explorations, laboratory analysis and results, and generate a geotechnical report with log of explorations in accordance with the information contained herein for all project structures, features, and utility systems. This report shall be the basis for the design of the Geotechnical related features of the project. The Geotechnical explorations, laboratory analysis/results, and report with log of borings shall include all areas necessary to design and build all features required in base pricing schedule and option pricing schedule items.

5 Specification Number & Drawing File Numbers

5.1 The general dwg file number shall be for each project task order.

5.2 The log of boring file number is: dependent on task order.

5.3 The topographic survey file number is; dependent on task order.

5.5 All drawings and all submittal documentation shall be digitized. Provide all digitized drawing deliverables in AutoDesk AutoCAD software, release 2004 compatible format and provide all other deliverables in MS WORD format. The contractor shall be responsible for design and drawings using computer-aided design and drafting (CADD) and delivering the two dimensional drawings in AutoDesk AutoCAD software, release 2004. The Government will only accept the final product for full operation, and on the target platform specified herein. The target platform is a Pentium 3.0 GHz, 512 MB Ram, and 40 GB Hard Drive with MicroSoft Windows XP operating system. Drawings produced by scanning drawings of record or containing photographic images shall be delivered in a raster format compatible with the target platform AutoCAD electronic

01 33 16 ‐5 digital format. Drawing files shall also be delivered in Portable Document Format (PDF).

Media for deliverables shall be Compact Disc (in CD-R). Compact discs shall be furnished in addition to hard copy drawings. Text height * for all Design drawings shall be minimum 1/8-inch high.

6 Design Quality Control Plan

6.1 The Contractor shall submit the Design Quality Control (DQC) Plan see Section 01

04.00 10 --- also cross reference to portions of this…