Specifications.pdf

SMYU 17-1067 Repair/Refurbish Building 1613, 2nd Floor and Structure, OSAN AB, KOREA

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 22 00

PAYMENT

PART 1 GENERAL

1.1 PAYMENT ITEM

1.1.1 Item 0001 - BLDG 1613 (Maintenance and Repair Work)

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION (Not Applicable)

-- End of Section Table of Contents --

SECTION 01 22 00 Page 1 and Structure_OSAN AB, KOREA

SECTION 01 22 00

PAYMENT

PART 1 GENERAL

1.1 PAYMENT ITEM

Payment items for the work of this contract for which contract lump sum payments will be made are listed in the Contractor Line Item Number (CLIN) Schedule and described below. All costs for items of work, which are not specifically mentioned to be included in a particular lump sum payment item, shall be included in the listed item most closely associated with the work involved. The price and payment made for each item listed shall constitute full compensation for furnishing all plant, labor, materials, and equipment, and performing any associated Contractor quality control, environmental protection, meeting safety requirements, tests and reports, contractor manpower reporting IAW UAI 37.590-100(e), and for performing all work required for which separate payment is not otherwise provided.

1.1.1 Item 0001 - BLDG 1613 (Maintenance and Repair Work)

Building 1613 (Maintenance and Repair Work) will be paid for at the contract price, complete in place and ready for use. The work includes removal of the 2nd floor plywood deck and ceiling to add new wood joists and strengthen the existing steel girders, and all incidental work items necessary for a complete and usable facility as per the drawings and specifications.

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION (Not Applicable)

-- End of Section --

SECTION 01 22 00 Page 2

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 PROJECT SCHEDULER QUALIFICATIONS

PART 2 PRODUCTS

2.1 SOFTWARE

2.1.1 Government Default Software

2.1.2 Contractor Software

2.1.2.1 Primavera

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 BASIS FOR PAYMENT AND COST LOADING

3.2.1 Activity Cost Loading

3.2.2 Withholdings / Payment Rejection

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

3.3.2 Activity Durations

3.3.3 Procurement Activities

3.3.4 Mandatory Tasks

3.3.5 Government Activities

3.3.6 Standard Activity Coding Dictionary

3.3.6.1 Workers Per Day (WRKP)

3.3.6.2 Responsible Party Coding (RESP)

3.3.6.3 Area of Work Coding (AREA)

3.3.6.4 Modification Number (MODF)

3.3.6.5 Bid Item Coding (BIDI)

3.3.6.6 Phase of Work Coding (PHAS)

3.3.6.7 Category of Work Coding (CATW)

3.3.6.8 Feature of Work Coding (FOW)

3.3.7 Contract Milestones and Constraints

3.3.7.1 Project Start Date Milestone and Constraint

3.3.7.2 End Project Finish Milestone and Constraint

3.3.7.3 Interim Completion Dates and Constraints

3.3.7.3.1 Start Phase

3.3.7.3.2 End Phase

3.3.8 Calendars

3.3.9 Open Ended Logic

3.3.10 Default Progress Data Disallowed

3.3.11 Out-of-Sequence Progress

3.3.12 Added and Deleted Activities

3.3.13 Original Durations

3.3.14 Leads, Lags, and Start to Finish Relationships

3.3.15 Retained Logic

SECTION 01 32 01.00 10 Page 1

3.3.16 Percent Complete

3.3.17 Remaining Duration

3.3.18 Cost Loading of Closeout Activities

3.3.18.1 As-Built Drawings

3.3.18.2 O & M Manuals

3.3.19 Anticipated Adverse Weather

3.3.20 Early Completion Schedule and the Right to Finish Early

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.5 SUBMISSION REQUIREMENTS

3.5.1 Data CD/DVDs

3.5.2 Narrative Report

3.5.3 Schedule Reports

3.5.3.1 Activity Report

3.5.3.2 Logic Report

3.5.3.3 Total Float Report

3.5.3.4 Earnings Report by CLIN

3.5.3.5 Schedule Log

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

3.6.2 Update Submission Following Progress Meeting

3.7 WEEKLY PROGRESS MEETINGS

3.8 FAILURE TO ACHIEVE PROGRESS

3.8.1 Artificially Improving Progress

3.8.2 Failure to Perform

3.8.3 Recovery Schedule

3.9 OWNERSHIP OF FLOAT

3.10 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

SECTION 01 32 01.00 10 Page 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) 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 information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Documentation showing qualifications of personnel preparing schedule reports.

Preliminary Project Schedule; G Initial Project Schedule; G Periodic Schedule Update; G

Two copies of the schedules showing codes, values, categories, numbers, items, etc., as required.

Periodic schedule updates schedules shall be submitted together with the monthly progress payment request.

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. Qualifications of this individual shall be submitted to the Contracting Officer for review with the Preliminary Project Schedule submission.

SECTION 01 32 01.00 10 Page 3

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.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15, SCHEDULE 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. 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.

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.

SECTION 01 32 01.00 10 Page 4

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 shall 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. Submission, review and acceptance of features require design completion

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

d. Long procurement activities

e. Submission and approval of O & M manuals.

f. Submission and approval of as-built drawings.

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

r. Contractor's pre-final inspection.

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

t. Government's pre-final inspection.

SECTION 01 32 01.00 10 Page 5

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

v. 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, 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. All Activity Codes shall be developed and assigned to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site: http://rms.usace.army.mil.

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

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 shall be 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, SECTION 01 32 01.00 10 Page 6

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 Contracting Officer, 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 USACE).

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.

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. Code proposed fast track design and construction phases proposed to allow filtering and organizing the schedule by fast track design and construction packages.

b. If the 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

SECTION 01 32 01.00 10 Page 7 include, but are not limited to 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.

3.3.7.2 End Project Finish Milestone and Constraint

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

The project schedule must be constrained 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. The start milestone shall be called "Start Phase X" where "X" refers to the phase of work.

SECTION 01 32 01.00 10 Page 8

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 sSeasonal 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 days provided in the contract clause TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. The assignment of the non-work days should be over a seven-day week since weather records are compiled on seven-day weeks, which will 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" must have no predecessor logic, and the last activity -"End Project" must have no successor logic.

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

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

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

SECTION 01 32 01.00 10 Page 10

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 Anticipated Adverse Weather

Paragraph applicable to contracts with clause entitled TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.

3.3.20 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required 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 manhours) and the Government agreeing that the schedule is reasonable and achievable.

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

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are 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.

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, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified

SECTION 01 32 01.00 10 Page 11

Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Periodic Schedule Updates

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

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

These updates will enable the Government to assess Contractor's progress.

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.

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.

SECTION 01 32 01.00 10 Page 12

SMYU 17-1067 RRepair/Refurbish Building 1613, 2nd Floor

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. This should 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 must be as directed by the Contracting Officer. Typically, reports shall contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format.

Provide 2 set(s) of hardcopy reports. 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 data date. This report must reflect 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. This report must also 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.

SECTION 01 32 01.00 10 Page 13

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 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. The meeting will last no longer than 8 hours. Provide a draft of the proposed narrative report and schedule data file to the Government a minimum of two workdays in advance of the meeting. The Contractor's Project Manager and scheduler must attend the meeting with the authorized representative of the Contracting Officer.

Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work. Following the periodic schedule update meeting, make corrections to the draft submission. Include only those changes approved by the Government in the submission and invoice for payment.

3.6.2 Update Submission Following Progress Meeting

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

3.7 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled PERIODIC SCHEDULE UPDATE MEETINGS for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks. Use the current approved schedule update for the purposes of this meeting and for the production and review of reports. At the weekly progress meeting, address the status of RFIs, RFPs and Submittals.

3.8 FAILURE TO ACHIEVE PROGRESS

Should the progress fall behind the approved project schedule for reasons other than those that are excusable within the terms of the contract, the Contracting Officer may require provision of a written recovery plan for approval. The plan must detail how progress will be made-up to include which activities will be accelerated by adding additional crews, longer work hours, extra work days, etc.

3.8.1 Artificially Improving Progress

Artificially improving progress by means such as, but not limited to, revising the schedule logic, modifying or adding constraints, shortening activity durations, or changing calendars in the project schedule is prohibited. Indicate assumptions made and the basis for any logic, constraint, duration and calendar changes used in the creation of the

SECTION 01 32 01.00 10 Page 14 recovery plan. Any additional resources, manpower, or daily and weekly work hour changes proposed in the recovery plan must be evident at the work site and documented in the daily report along with the Schedule Narrative Report.

3.8.2 Failure to Perform

Failure to perform work and maintain progress in accordance with the supplemental recovery plan may result in an interim and final unsatisfactory performance rating and/or may result in corrective action directed by the Contracting Officer pursuant to FAR 52.236-15 Schedules for Construction Contracts, FAR 52.249-10 Default (Fixed-Price Construction), and other contract provisions.

3.8.3 Recovery Schedule

Should the Contracting Officer find it necessary, submit a recovery schedule pursuant to FAR 52.236-15 Schedules for Construction Contracts.

3.9 OWNERSHIP OF FLOAT

Except for the provision given in the paragraph IMPACT TO EARLY COMPLETION SCHEDULE, float available in the schedule, at any time, shall not be considered for the exclusive use of either the Government or the Contractor including activity and/or project float. Activity float is the number of work days that an activity can be delayed without causing a delay to the "End Project" finish milestone. Project float (if applicable) is the number of work days between the projected early finish and the contract completion date milestone.

3.10 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

Import the schedule data into the Quality Control System (QCS) and export the QCS data to the Government. This data is considered to be additional supporting data in a form and detail required by the Contracting Officer pursuant to FAR 52.232-5 - Payments under Fixed-Price Construction Contracts. The receipt of a proper payment request pursuant to FAR 52.232-27 - Prompt Payment for Construction Contracts is contingent upon the Government receiving both acceptable and approvable hard copies and matching electronic export from QCS of the application for progress payment.

SECTION 01 32 01.00 10 Page 15

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 33 00

SUBMITTAL PROCEDURES

PART 1 GENERAL

1.1 SUMMARY

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

1.2.2 Approving Authority

1.2.3 Work

1.3 SUBMITTALS

1.4 SUBMITTAL CLASSIFICATION

1.4.1 Government Approved

1.4.2 Information Only

1.5 PREPARATION

1.5.1 Transmittal Form

1.5.2 Identifying Submittals

1.5.3 Format for SD-02 Shop Drawings

1.5.4 Format of SD-03 Product Data and SD-08 Manufacturer's

Instructions

1.5.5 Format of SD-04 Samples

1.5.6 Format of SD-05 Design Data and SD-07 Certificates

1.5.7 Format of SD-06 Test Reports and SD-09 Manufacturer's Field

Reports

1.5.8 Format of SD-10 Operation and Maintenance Data (O&M)

1.5.9 Format of SD-01 Preconstruction Submittals and SD-11 Closeout

Submittals

1.6 QUANTITY OF SUBMITTALS

1.6.1 Number of Copies of SD-02 Shop Drawings

1.6.2 Number of Copies of SD-03 Product Data and SD-08

Manufacturer's Instructions

1.6.3 Number of Samples SD-04 Samples

1.6.4 Number of Copies SD-05 Design Data and SD-07 Certificates

1.6.5 Number of Copies SD-06 Test Reports and SD-09 Manufacturer's

Field Reports

1.6.6 Number of Copies of SD-10 Operation and Maintenance Data

1.6.7 Number of Copies of SD-01 Preconstruction Submittals and SD-11

Closeout Submittals

1.7 INFORMATION ONLY SUBMITTALS

1.8 VARIATIONS

1.8.1 Considering Variations

1.8.2 Proposing Variations

1.8.3 Warranting That Variations Are Compatible

1.8.4 Review Schedule Is Modified

1.9 SUBMITTAL REGISTER

1.9.1 Use of Submittal Register

1.9.2 Contractor Use of Submittal Register

1.9.3 Approving Authority Use of Submittal Register

1.9.4 Action Codes

1.9.4.1 Government Review Action Codes

1.9.5 Copies Delivered to the Government

SECTION 01 33 00 Page 1

1.10 SCHEDULING

1.11 GOVERNMENT APPROVING AUTHORITY

1.12 DISAPPROVED OR REJECTED SUBMITTALS

1.13 APPROVED/ACCEPTED SUBMITTALS

1.14 APPROVED SAMPLES

1.15 WITHHOLDING OF PAYMENT

1.16 PROGRESS SCHEDULE

1.16.1 Bar Chart

1.16.2 Project Network Analysis

1.17 STATUS REPORT ON MATERIALS ORDERS

1.18 STAMPS

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 33 00 Page 2

SECTION 01 33 00

SUBMITTAL PROCEDURES

PART 1 GENERAL

1.1 SUMMARY

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 are to be the same as those used in the contract drawings.

Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

Contractor's Quality Control (CQC) System Manager to check and approve all items prior to submittal and stamp, sign, and date indicating action taken. Proposed deviations from the contract requirements are to be clearly identified. Include within submittals 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 are to be scheduled and made prior to the acquisition of the material or equipment covered thereby. Pick up and dispose of samples not incorporated into the work in accordance with manufacturer's Material Safety Data Sheets (MSDS) and in compliance with existing laws and regulations.

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

Submittals requirements are specified in the technical sections.

Submittals are identified by Submittal Description (SD) numbers and titles as follows:

SD-01 Preconstruction Submittals

Submittals which are required prior to start of construction (work) or the start of the next major phase of the construction on a multi-phase contract, includes schedules, tabular list of data, or tabular list including location, features, or other pertinent information regarding products, materials, equipment, or components to be used in the work.

Certificates of insurance

Surety bonds

List of proposed Subcontractors

SECTION 01 33 00 Page 3

List of proposed products

Construction Progress Schedule

Network Analysis Schedule (NAS)

Submittal register

Schedule of prices

Health and safety plan

Work plan

Quality Control(QC) 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, systems or equipment for some portion of the work.

Samples of warranty language when the contract requires extended product warranties.

SD-04 Samples

Fabricated or unfabricated 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

Design calculations, mix designs, analyses or other data pertaining to

SECTION 01 33 00 Page 4 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 logs and 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 manufacturer, 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.

Text of posted operating instructions.

SD-08 Manufacturer's Instructions

Preprinted material describing installation of a product, system or material, including special notices and (MSDS)concerning impedances, hazards and safety precautions.

SD-09 Manufacturer's Field Reports

Documentation of the testing and verification actions taken by manufacturer's representative at the job site, in the vicinity of the job site, or on a sample taken from the job site, on a portion of the work, during or after installation, to confirm compliance with manufacturer's standards or instructions. The documentation must be signed by an authorized official of a testing laboratory or agency and must state the test results; and indicate whether the material, product, or system has passed or failed the test.

SECTION 01 33 00 Page 5

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, including manufacturer's help and product line documentation necessary to maintain and install equipment. This data is needed by operating and maintenance personnel for the safe and efficient operation, maintenance and repair of the item.

This data is intended to be incorporated in an operations and maintenance manual or control system.

SD-11 Closeout Submittals

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

Special requirements necessary to properly close out a construction contract. For example, Record Drawings and as-built drawings. Also, submittal requirements necessary to properly close out a major phase of construction on a multi-phase contract.

Interim "DD Form 1354" with cost breakout for all assets 30 days prior to facility turnover.

1.2.2 Approving Authority

Office or designated person authorized to approve submittal.

1.2.3 Work

As used in this section, on- and off-site construction required by contract documents, including labor necessary to produce submittals, except those SD-01 Pre-Construction Submittals noted above, construction, materials, products, equipment, and systems incorporated or to be incorporated in such construction.

1.3 SUBMITTALS

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

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with this section.

SD-01 Preconstruction Submittals

Submittal Register; G

1.4 SUBMITTAL CLASSIFICATION

Submittals are classified as follows:

1.4.1 Government Approved

Government approval is required for extensions of design, critical materials, deviations, equipment whose compatibility with the entire system

SECTION 01 33 00 Page 6 must be checked, and other items as designated by the Contracting Officer.

Within the terms of the Contract Clause entitled, "Specifications and Drawings for Construction," they are considered to be "shop drawings."

1.4.2 Information Only

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

1.5.1 Transmittal Form

Use the attached sample transmittal form (ENG Form 4025) 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. Properly complete this form by filling out all the heading blank spaces and identifying each item submitted. Exercise special care to ensure proper listing of the specification paragraph and sheet number of the contract drawings pertinent to the data submitted for each item.

1.5.2 Identifying Submittals

When submittals are provided by a Subcontractor, the Prime Contractor is to prepare, review and stamp with Contractor's approval all specified submittals prior to submitting for Government approval.

Identify submittals, except sample installations and sample panels, with the following information permanently adhered to or noted on each separate component of each submittal and noted on transmittal form. Mark each copy of each submittal identically, with the following:

a. Project title and location.

b. Construction contract number.

c. Date of the drawings and revisions.

d. Name, address, and telephone number of subcontractor, supplier, manufacturer and any other subcontractor associated with the submittal.

e. Section number of the specification section by which submittal is required.

f. Submittal description (SD) number of each component of submittal.

g. When a resubmission, add alphabetic suffix on submittal description, for example, submittal 18 would become 18A, to indicate resubmission.

h. Product identification and location in project.

1.5.3 Format for SD-02 Shop Drawings

Shop drawings are not to be less than 210 by 297 mm (8 1/2 by 11 inches) nor more than 1189 by 841 mm (30 by 42 inches), except for full size patterns or templates. Prepare drawings to accurate size, with scale indicated, unless other form is required. Drawings are to be suitable for

SECTION 01 33 00 Page 7 reproduction and be of a quality to produce clear, distinct lines and letters with dark lines on a white background.

Present 210 by 297 mm (8 1/2 by 11 inches) sized shop drawings as part of the bound volume for submittals required by section. Present larger drawings in sets.

Include on each drawing the drawing title, number, date, and revision numbers and dates, in addition to information required in paragraph entitled, "Identifying Submittals," of this section.

Number drawings in a logical sequence. Contractors may use their own number system. Each drawing is to bear the number of the submittal in a uniform location adjacent to the title block. Place the Government contract number in the margin, immediately below the title block, for each drawing.

Reserve a blank space, no smaller than 1150 mm x 800 mm (4.5 inches x 3 inches) on the right hand side of each sheet for the Government disposition stamp.

Dimension drawings, except diagrams and schematic drawings; prepare drawings demonstrating interface with other trades to scale. Use the same unit of measure for shop drawings as indicated on the contract drawings.

Identify materials and products for work shown.

Include the nameplate data, size and capacity on drawings. Also include applicable federal, military, industry and technical society publication references.

1.5.4 Format of SD-03 Product Data and SD-08 Manufacturer's Instructions

Present product data submittals for each section as a complete, bound volume. Include table of contents, listing page and catalog item numbers for product data.

Indicate, by prominent notation, each product which is being submitted;

indicate…