J5. B1 Concrete Repair Specifications.pdf

Building One Structural Repairs NIST

Section 00 01 15 Page 1

SECTION 00 01 15

LIST OF DRAWINGS

02/11

PART 1 GENERAL

1.1 SUMMARY

This section lists the drawings for the project.

1.2 CONTRACT DRAWINGS

Contract drawings are as follows:

DRAWING NO. REVISION NO. TITLE

S0.0 0 TITLE SHEET

S0.1 0 STRUCTURAL NOTES

S0.2 0 STRUCTURAL NOTES

S1.0 0 BASE BID: BASEMENT PLAN

S2.0 0 BASE BID: ENTRANCE STRUCTURAL CONCRETE REPAIRS

S2.1 0 BASE BID: ELEVATIONS

S2.2 0 BASE BID: DETAILS

S2.3 0 BASE BID: DETAILS

S3.0 0 BID OPTION 1: CONCRETE COATINGS

S3.1 0 BID OPTION 1: ELEVATIONS

S3.2 0 BID OPTION 1: ELEVATIONS

S3.3 0 BID OPTION 1: ELEVATIONS

-- End of Section --

Section 00 22 13.00 20 Page 1

SECTION 00 22 13.00 20

SUPPLEMENTARY INSTRUCTIONS TO OFFERORS

02/14

PART 1 GENERAL

Not used.

PART 2 PRODUCTS

PART 3 EXECUTION

Section 01 11 00 Page 1

SECTION 01 11 00

SUMMARY OF WORK

08/15

PART 1 GENERAL

1.1 SUBMITTALS

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

submittals not having a "G" designation are for information only. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Utility Outage Requests; G

Utility Connection Requests; G

Excavation Permits;

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The work includes NIST Building 1 Concrete Repairs, as shown in the construction documents, and incidental related work.

1.2.2 Location

The work is located at the NIST Boulder Campus, 325 Broadway, Boulder, CO;

Building 1., approximately as indicated. The exact location will be shown by the Contracting Officer or Contracting Officer Representative.

1.3 CONTRACT DRAWINGS

The following drawings accompany this specification and are a part thereof.

Sheets 1 through 12. Contract documents are provided electronically and reproduced at the Contractor’s expense. Reference publications will not be furnished. Immediately check documents and notify the Government of any discrepancies.

1.4 WORK RESCHEDULING

Normal duty hours for work are from 7 a.m. to 5 p.m., Monday through Friday.

Requests for additional work requires written approval from the Contracting Officer or Contracting Officer Representative 10 days in advance of the proposed work period.

1.5 OCCUPANCY OF PREMISES

Building(s) will be occupied during performance of work under this Contract.

Section 01 11 00 Page 2

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

1.6 ON-SITE PERMITS

Reference NIST Safety Plan Requirements Checklist for all written requirements.

1.6.1 Utility Outage Requests and Utility Connection Requests

Schedule work to minimize outages. For utility outages and connections required during the execution of work that affect existing systems, schedule outside the regular working hours or on weekends, as approved by the Contracting Officer or Contracting Officer Representative. Schedule utility outages and connections to minimize disruptions to the Government. No additional payment will be provided for utility outages and connections required to be performed outside the regular work hours.

Submit requests for utility outages and connections in writing to the Contracting Officer or Contracting Officer Representative for approval at least 10 calendar days in advance of the time required. In each request, state the system involved, area involved, approximate duration of outage, and the nature of work involved.

1.7 LOCATION OF UNDERGROUND UTILITIES

Obtain digging permits prior to start of excavation, and comply with Reference NIST Safety Plan Requirements Checklist – Excavation & Trenching for locating and marking underground utilities. Contact local utility locating service a minimum of 48 hours prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work.

1.8.1 Notification Prior to Excavation

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

Section 01 14 00 Page 1

SECTION 01 14 00

WORK RESTRICTIONS

11/11

PART 1 GENERAL

1.1 CONTRACTOR ACCESS AND USE OF PREMISES

1.1.1 Activity Regulations

Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear hard hats in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry.

Mark Contractor equipment for identification.

1.1.2 No Smoking Policy

Smoking is prohibited inside and outside of all buildings. This applies to existing buildings, buildings under construction and buildings under renovation.

1.1.4 Working Hours

Regular working hours are between 7 a.m. and 5 p.m., Monday through Friday, excluding Government holidays.

1.1.5 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer or Contracting Officer Representative approval. Make application 10 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title.

Based on the justification provided, the Contracting Officer or Contracting Officer Representative may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer or Contracting Officer Representative. Make utility cutovers after normal working hours or on Saturdays, Sundays, and Government holidays unless directed otherwise.

1.1.6 Occupied Building

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

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

1.1.7 Utility Cutovers and Interruptions

a. Make utility cutovers and interruptions after normal working hours or on Saturdays, Sundays, and Government holidays. Conform to procedures required in paragraph WORK OUTSIDE REGULAR HOURS.

Section 01 14 00 Page 2

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

c. Interruption to water, sanitary sewer, storm sewer, telephone service, electric service, air conditioning, heating, fire alarm, and compressed air are considered utility cutovers pursuant to the paragraph WORK

OUTSIDE REGULAR HOURS.

d. Operation of Station Utilities: The Contractor must not operate nor disturb the setting of control devices in the station utilities system, including water, sewer, electrical, and steam services. The Government will operate the control devices as required for normal conduct of the work. The Contractor must notify the Contracting Officer or Contracting Officer Representative giving reasonable advance notice when such operation is required.

e. Connection to Existing Sanitary Sewer Line: Provide positive verification that the existing line conveys sanitary sewer; verify line is not incorrectly connected to a storm drain.

Not Used

-- End of Section

Section 01 30 00 Page 1

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

08/15

PART 1 GENERAL

1.1 REFERENCES

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

15 CFR 772 Definition of Terms

15 CFR 773 Special Licensing Procedures

1.2 SUBMITTALS

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

View Location Map;

Progress and Completion Pictures;

1.3 VIEW LOCATION MAP

Submit, prior to or with the first digital photograph submittals, a sketch or drawing indicating the required photographic locations. Update as required if the locations are moved.

1.4 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color, minimum resolution in JPEG file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project. Indicate photographs demonstrating environmental procedures. Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file. Include a date designator in file names.

Cross reference submittals in the appropriate daily report. Photographs provided are for unrestricted use by the Government.

1.5 MINIMUM INSURANCE REQUIREMENTS

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

Section 01 32 01.00 10 Page 1

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

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

1.2 SUBMITTALS

Project Scheduler Qualifications; G

Preliminary Project Schedule; G

Initial Project Schedule; G

Periodic Schedule Update; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

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

Representative must have a comprehensive knowledge of CPM scheduling principles and application.

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

Section 01 32 01.00 10 Page 2 available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.

2.1.2.1 Primavera

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

2.1.2.2 Other Than Primavera

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

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. 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 or Contracting Officer Representative.

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 or Contracting Officer Representative will consider, but is not limited to, the

Section 01 32 01.00 10 Page 3 following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

Less than 2 percent of all non-procurement activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

3.3.3 Procurement Activities

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

3.3.4 Mandatory Tasks

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

a. Submission, review and acceptance of SD-01 Preconstruction Submittals

(individual activity for each).

b. 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. Performance Verification testing.

h. Other systems testing, if required.

i. Government's pre-final inspection.

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

k. Final inspection.

3.3.5 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

Section 01 32 01.00 10 Page 4 herein. Submit additional constraints to the Contracting Officer or Contracting Officer Representative for approval on a case by case basis.

3.3.6.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.6.2 End Project Finish Milestone and Constraint

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

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

3.3.6.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.6.3.1 Start Phase

Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work.

3.3.6.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.7 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 adverse weather delay work days provided in the Special Contract Clauses . Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends.

3.3.8 Open Ended Logic

Section 01 32 01.00 10 Page 5

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

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

3.3.9 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.10 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 or Contracting Officer Representative. 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.11 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 or Contracting Officer Representative. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer or Contracting Officer Representative approval.

3.3.12 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 or Contracting Officer Representative.

3.3.13 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.14 Retained Logic

Section 01 32 01.00 10 Page 6

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.15 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.16 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.17 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.17.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 5 percent of the present contract value. Activity will be declared 100 percent complete upon the Government's acceptance of substantially complete work and final approval of all necessary closeout documentation to include, but not limited to: reports, submittals, payrolls, and drawings.

3.4 PROJECT SCHEDULE SUBMISSIONS

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 Initial Project Schedule Submission

Submit the Initial Baseline Project Schedule for approval within 5 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. All work to be within the contract period of performance.

Section 01 32 01.00 10 Page 7

3.4.2 Periodic Schedule Updates

Provide updated three week schedule at the weekly construction progress 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 Electronic Submission

Provide an electronic submittal containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include the Narrative Report and all required Schedule Reports. 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.

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

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

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

3.5.3 Schedule Reports

Section 01 32 01.00 10 Page 8

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer or Contracting Officer Representative. Typically, reports contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format. Provide 3 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, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

3.5.3.5 Schedule Log

Provide a Scheduling/Leveling Report generated from the current project schedule being submitted.

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

Section 01 32 01.00 10 Page 9 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 or Contracting Officer Representative. 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. Distribute meeting minutes be for comment and correction no later than two working days after the meeting.

3.8 REQUESTS FOR TIME EXTENSIONS

Provide a justification of delay to the Contracting Officer or Contracting Officer Representative in accordance with the contract provisions and clauses for approval within 10 days of a delay occurring. Also prepare a time impact analysis for each Government request for proposal (RFP) to justify time extensions.

3.8.1 Justification of Delay

Provide a description of the event(s) that caused the delay and/or impact to the work. As part of the description, identify all schedule activities impacted. Show that the event that caused the delay/impact was the responsibility of the Government. Provide a time impact analysis that demonstrates the effects of the delay or impact on the project completion date or interim completion date(s). Evaluate multiple impacts chronologically; each with its own justification of delay. With multiple impacts consider any concurrency of delay. A time extension and the schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer or Contracting Officer Representative.

3.8.2 Time Extension

The Contracting Officer or Contracting Officer Representative must approve the Justification of Delay including the time impact analysis before a time extension will be granted. No time extension will be granted unless the delay consumes all available Project Float and extends the projected finish

Section 01 32 01.00 10 Page 10 date ("End Project" milestone) beyond the Contract Completion Date. The time extension will be in calendar days.

Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay will not be a cause for an extension to the performance period, completion date, or any interim milestone date.

3.8.3 Impact to Early Completion Schedule

No extended overhead will be paid for delay prior to the original Contract Completion Date for an Early Completion IPS unless the Contractor actually performed work in accordance with that Early Completion Schedule. The Contractor must show that an early completion was achievable had it not been for the impact.

3.9 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 or Contracting Officer Representative 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.9.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 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.9.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 may result in corrective action directed by the Contracting Officer or Contracting Officer Representative pursuant to FAR 52.236-15 Schedules for Construction Contracts, FAR 52.249-10 Default (Fixed- Price Construction), and other contract provisions.

3.9.3 Recovery Schedule

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

3.10 OWNERSHIP OF FLOAT

Except for the provision given in the paragraph IMPACT TO EARLY COMPLETION SCHEDULE, float available in the schedule, at any time, may 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

Section 01 32 01.00 10 Page 11 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.11 PRIMAVERA P6 MANDATORY REQUIREMENTS

If Primavera P6 is being used, request a backup file template (.xer) from the Government, if one is available, prior to building the schedule. The following settings are mandatory and required in all schedule submissions to the Government:

a. Activity Codes must be Project Level, not Global or EPS level.

b. Calendars must be Project Level, not Global or Resource level.

c. Activity Duration Types must be set to "Fixed Duration & Units".

d. Percent Complete Types must be set to "Physical".

e. Time Period Admin Preferences must remain the default "8.0 hr/day, 40 hr/week, 172 hr/month, 2000 hr/year". Set Calendar Work Hours/Day to 8.0 Hour days.

f. Set Schedule Option for defining Critical Activities to "Longest Path".

g. Set Schedule Option for defining progressed activities to "Retained

Logic".

h. Set up cost loading using a single lump sum labor resource. The Price/Unit must be $1/hr, Default Units/Time must be "8h/d", and settings "Auto Compute Actuals" and "Calculate costs from units" selected.

i. Activity ID's must not exceed 10 characters.

j. Activity Names must have the most defining and detailed description within the first 30 characters.

Section 01 33 00 Page 1

SECTION 01 33 00

SUBMITTAL PROCEDURES

08/18

PART 1 GENERAL

1.1 SUMMARY

1.1.1 Submittal Information

The Contracting Officer or Contracting Officer Representative may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections. Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

Units of weights and measures used on all submittals are to be the same as those used in the contract drawings.

1.1.2 Project Type

The Contractor's Quality Control (CQC) System Manager is to check and approve all items before 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.

The Contractor and the Designer of Record (DOR), if applicable, are to check and approve all items before 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.

1.1.3 Submission of Submittals

Schedule and provide submittals requiring Government approval before acquiring the material or equipment covered thereby. Pick up and dispose of samples not incorporated into the work in accordance with manufacturer's Safety Data Sheets (SDS) and in compliance with existing laws and regulations.

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

Submittal requirements are specified in the technical sections. Examples and descriptions of submittals identified by the Submittal Description (SD) numbers and titles follow:

Section 01 33 00 Page 2

Submittals that are required prior to or commencing with the start of work on site.

Preconstruction Submittals include schedules and a tabular list of locations, features, and other pertinent information regarding products, materials, equipment, or components to be used in the work.

Certificates Of Insurance

Surety Bonds

List Of Proposed Subcontractors

List Of Proposed Products

Submittal Register

Schedule Of Prices Or Earned Value Report

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.

Section 01 33 00 Page 3

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 ensuring work can be judged. Includes assemblies or portions of assemblies that are to be incorporated into the project and those that will be removed at conclusion of the work.

SD-05 Design Data

Design 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. Unless specified in another section, testing must have been within three years of date of contract award for the project.

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

Report that 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 the 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 document purpose is to further promote the 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 (SDS)concerning impedances, hazards and safety precautions.

Section 01 33 00 Page 4

SD-10 Operation and Maintenance Data

Data provided by the manufacturer, or the system provider, including manufacturer's help and product line documentation, necessary to maintain and install equipment, for operating and maintenance use by facility personnel.

Data required by operating and maintenance personnel for the safe and efficient operation, maintenance and repair of the item.

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

Submittals required for Guiding Principle Validation (GPV) or Third Party Certification (TPC).

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.

1.2.2 Approving Authority

Office or designated person authorized to approve the submittal.

1.2.3 Work

As used in this section, on-site 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. In exception, excludes work to produce SD-01 submittals.

1.3 SUBMITTALS

following in accordance with this section.

Submittal Register; G

1.4 SUBMITTAL CLASSIFICATION

1.4.1 Government Approved (G)

Government approval is required for extensions of design, critical materials, variations, equipment whose compatibility with the entire system must be checked, and other items as designated by the Government.

Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, submittals are considered to be "shop drawings."

Section 01 33 00 Page 5

1.4.2 For Information Only

Submittals not requiring Government approval will be for information only.

Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, they are not considered to be "shop drawings."

1.5 PREPARATION

1.5.1 Transmittal Form

Transmit each submittal, except sample installations and sample panels to the office of the approving authority using the transmittal form prescribed by the Contracting Officer or Contracting Officer Representative. Include all information prescribed by the transmittal form and required in paragraph IDENTIFYING SUBMITTALS. Use the submittal transmittal forms to record actions regarding samples.

1.5.2 Identifying Submittals

The Contractor's Quality Control Manager must prepare, review and stamp submittals, including those provided by a subcontractor, before submittal to the Government.

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. Dates 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 by which submittal is required

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

g. For 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 Submittal Format

1.5.3.1 Format of SD-01 Preconstruction Submittals

When the submittal includes a document that is to be used in the project, or is to become part of the project record, other than as a submittal, do not apply the Contractor's approval stamp to the document itself, but to a separate sheet accompanying the document.

Provide data in the unit of measure used in the contract documents.

Section 01 33 00 Page 6

1.5.3.2 Format for SD-02 Shop Drawings

Provide shop drawings not less than 8 1/2 by 11 inches nor more than 30 by 42 inches, except for full-size patterns or templates. Prepare drawings to accurate size, with scale indicated, unless another form is required. Ensure drawings are suitable for reproduction and of a quality to produce clear, distinct lines and letters, with dark lines on a white background.

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

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

Present shop drawings sized 8 1/2 by 11 inches as part of the bound volume for submittals. Present larger drawings in sets. Submit an electronic copy of drawings in PDF format.

1.5.3.2.1 Drawing Identification

Include on each drawing the drawing title, number, date, and revision numbers and dates, in addition to information required in paragraph IDENTIFYING

SUBMITTALS.

Number drawings in a logical sequence. Each drawing is to bear the number of the submittal in a uniform location next 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 2 inches on the right-hand side of each sheet for the Government disposition stamp.

1.5.3.3 Format of SD-03 Product Data

Present product data submittals for each section as a complete, bound volume.

Include a table of contents, listing the page and catalog item numbers for product data.

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

indicate the specification section number and paragraph number to which it pertains.

1.5.3.3.1 Product Information

Supplement product data with material prepared for the project to satisfy the submittal requirements where product data does not exist. Identify this material as developed specifically for the project, with information and format as required for submission of SD-07 Certificates.

Provide product data in units used in the Contract documents. Where product data are included in preprinted catalogs with another unit, submit the dimensions in contract document units, on a separate sheet.

Section 01 33 00 Page 7

1.5.3.3.2 Standards

Where equipment or materials are specified to conform to industry or technical-society reference standards of such organizations as the American National Standards Institute (ANSI), ASTM International (ASTM), National Electrical Manufacturer's Association (NEMA), Underwriters Laboratories (UL), or Association of Edison Illuminating Companies (AEIC), submit proof of such compliance. The label or listing by the specified organization will be acceptable evidence of compliance. In lieu of the label or listing, submit a certificate from an independent testing organization, competent to perform testing, and approved by the Contracting Officer or Contracting Officer Representative. State on the certificate that the item has been tested in accordance with the specified organization's test methods and that the item complies with the specified organization's reference standard.

1.5.3.3.3 Data Submission

Collect required data submittals for each specific material, product, unit of work, or system into a single submittal that is marked for choices, options, and portions applicable to the submittal. Mark each copy of the product data identically. Partial submittals will not be accepted for expedition of the construction effort.

Submit the manufacturer's instructions before installation.

1.5.3.4 Format of SD-04 Samples

1.5.3.4.1 Sample Characteristics

Furnish samples in the following sizes, unless otherwise specified or unless the manufacturer has prepackaged samples of approximately the same size as specified:

a. Sample of Equipment or Device: Full size.

b. Sample of Materials Less Than 2 by 3 inches: Built up to 8 1/2 by 11 inches.

c. Sample of Materials Exceeding 8 1/2 by 11 inches: Cut down to 8 1/2 by 11 inches and adequate to indicate color, texture, and material variations.

d. Sample of Linear Devices or Materials: 10 inch length or length to be supplied, if less than 10 inches. Examples of linear devices or materials are conduit and handrails.

e. Sample Volume of Nonsolid Materials: Pint. Examples of nonsolid materials are sand and paint.

f. Color Selection Samples: 2 by 4 inches. Where samples are specified for selection of color, finish, pattern, or texture, submit the full set of available choices for the material or product specified. Sizes and quantities of samples are to represent their respective standard unit.

g. Sample Panel: 4 by 4 feet.

h. Sample Installation: 100 square feet.

Section 01 33 00 Page 8

1.5.3.4.2 Sample Incorporation

Reusable Samples: Incorporate returned samples into work only if so specified or indicated. Incorporated samples are to be in undamaged condition at the time of use.

Recording of Sample Installation: Note and preserve the notation of any area constituting a sample installation, but remove the notation at…