Appendix_4_-_Additional_Division_1_Specifications.pdf

DIVISION 1 SPECIFICATIONS

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

1.2 QUALIFICATIONS

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 BASIS FOR PAYMENT

3.3 PROJECT SCHEDULE

3.3.1 Use of the Critical Path Method

3.3.2 Level of Detail Required

3.3.2.1 Activity Durations

3.3.2.2 Procurement Activities

3.3.2.3 Critical Activities

3.3.2.4 Responsibility

3.3.2.5 Work Areas

3.3.2.6 Modification or Claim Number

3.3.2.7 Bid Item

3.3.2.8 Phase of Work

3.3.2.9 Feature of Work

3.3.3 Scheduled Project Completion

3.3.3.1 Project Start Date

3.3.3.2 Constraint of Last Activity

3.3.3.3 Early Project Completion

3.3.4 Interim Completion Dates

3.3.4.1 Start Phase

3.3.4.2 End Phase

3.3.4.3 Phase X

3.3.5 Default Progress Data Disallowed

3.3.6 Out-of-Sequence Progress

3.3.7 Negative Lags

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary Project Schedule Submission

3.4.2 Initial Project Schedule Submission

3.4.3 Periodic Schedule Updates

3.4.4 Standard Activity Coding Dictionary

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data Disks

3.5.1.1 File Medium

3.5.1.2 Disk Label

3.5.1.3 File Name

3.5.2 Narrative Report

01 32 01.00 10 -1

3.5.3 Approved Changes Verification

3.5.4 Schedule Reports

3.5.4.1 Activity Report

3.5.4.2 Logic Report

3.5.4.3 Total Float Report

3.5.4.4 Earnings Report

3.5.5 Network Diagram

3.5.5.1 Continuous Flow

3.5.5.2 Project Milestone Dates

3.5.5.3 Critical Path

3.5.5.4 Banding

3.5.5.5 S-Curves

3.6 PERIODIC PROGRESS MEETINGS

3.6.1 Meeting Attendance

3.6.2 Update Submission Following Progress Meeting

3.6.3 Progress Meeting Contents

3.6.3.1 Start and Finish Dates

3.6.3.2 Time Completion

3.6.3.3 Cost Completion

3.6.3.4 Logic Changes

3.6.3.5 Other Changes

3.7 REQUESTS FOR TIME EXTENSIONS

3.7.1 Justification of Delay

3.7.2 Submission Requirements

3.7.3 Additional Submission Requirements

3.8 DIRECTED CHANGES

3.9 OWNERSHIP OF FLOAT

-- End of Section Table of Contents --

01 32 01.00 10 -2

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 QUALIFICATIONS

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

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

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

3.2 BASIS FOR PAYMENT

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

3.3 PROJECT SCHEDULE

The computer software system utilized by the Contractor to produce the

01 32 01.00 10 -3

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

3.3.1 Use of the Critical Path Method

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

3.3.2 Level of Detail Required

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

3.3.2.1 Activity Durations

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

3.3.2.2 Procurement Activities

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

3.3.2.3 Critical Activities

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

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

b. Submission and approval of O & M manuals.

c. Submission and approval of as-built drawings.

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

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

f. Submission of TAB specialist design review report.

g. Submission and approval of fire protection specialist.

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

01 32 01.00 10 -4 commissioning plans and data.

i. Air and water balance dates.

j. HVAC commissioning dates.

k. Controls testing plan.

l. Controls testing.

m. Performance Verification testing.

n. Other systems testing, if required.

o. Prefinal inspection.

p. Correction of punchlist from prefinal inspection.

q. Final inspection.

3.3.2.4 Responsibility

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

3.3.2.5 Work Areas

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

3.3.2.6 Modification or Claim Number

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

Existing activities shall not normally be changed to reflect modifications.

3.3.2.7 Bid Item

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

3.3.2.8 Phase of Work

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

01 32 01.00 10 -5

3.3.2.9 Feature of Work

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

3.3.3 Scheduled Project Completion

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

3.3.3.1 Project Start Date

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

3.3.3.2 Constraint of Last Activity

Completion of the last activity in the schedule shall be constrained by the contract completion date. Calculation on project updates shall be such that if the early finish of the last activity falls after the contract completion date, then the float calculation shall reflect a negative float on the critical path. The Contractor shall include as the last activity in the project schedule an activity called "End Project". The "End Project" activity shall have an "LF" constraint date equal to the completion date for the project, and a zero day duration.

3.3.3.3 Early Project Completion

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

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

3.3.4 Interim Completion Dates

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

3.3.4.1 Start Phase

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

3.3.4.2 End Phase

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

01 32 01.00 10 -6

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

3.3.4.3 Phase X

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

3.3.5 Default Progress Data Disallowed

Actual Start and Finish dates shall not be automatically updated by default mechanisms that may be included in CPM scheduling software systems. Actual Start and Finish dates on the CPM schedule shall match those dates provided from Contractor Quality Control Reports. Failure of the Contractor to document the Actual Start and Finish dates on the Daily Quality Control report for every in-progress or completed activity, and failure to ensure that the data contained on the Daily Quality Control reports is the sole basis for schedule updating shall result in the disapproval of the Contractor's schedule and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes.

3.3.6 Out-of-Sequence Progress

Activities that have posted progress without all preceding logic being satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case approval of the Contracting Officer. The Contractor shall propose logic corrections to eliminate all out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule.

3.3.7 Negative Lags

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

3.4 PROJECT SCHEDULE SUBMISSIONS

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

3.4.1 Preliminary Project Schedule Submission

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

3.4.2 Initial Project Schedule Submission

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

01 32 01.00 10 -7

3.4.3 Periodic Schedule Updates

Based on the result of progress meetings, specified in "Periodic Progress Meetings," the Contractor shall submit periodic schedule updates. These submissions shall enable the Contracting Officer to assess Contractor's progress. If the Contractor fails or refuses to furnish the information and project schedule data, which in the judgment of the Contracting Officer or authorized representative is necessary for verifying the Contractor's progress, the Contractor shall be deemed not to have provided an estimate upon which progress payment may be made.

3.4.4 Standard Activity Coding Dictionary

The Contractor shall use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11, Appendix A. This exact structure is mandatory, even if some fields are not used.

3.5 SUBMISSION REQUIREMENTS

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

3.5.1 Data Disks

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

3.5.1.1 File Medium

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

3.5.1.2 Disk Label

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

3.5.1.3 File Name

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

3.5.2 Narrative Report

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

01 32 01.00 10 -8 required to be taken. The narrative report is expected to relay to the Government, the Contractor's thorough analysis of the schedule output and its plans to compensate for any problems, either current or potential, which are revealed through that analysis.

3.5.3 Approved Changes Verification

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

3.5.4 Schedule Reports

The format for each activity for the schedule reports listed below shall contain: Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float. Actual Start and Actual Finish Dates shall be printed for those activities in progress or completed.

3.5.4.1 Activity Report

A list of all activities sorted according to activity number.

3.5.4.2 Logic Report

A list of Preceding and Succeeding activities for every activity in ascending order by activity number. Preceeding and succeeding activities shall include all information listed above in paragraph Schedule Reports.

A blank line shall be left between each activity grouping.

3.5.4.3 Total Float Report

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

3.5.4.4 Earnings Report

A compilation of the Contractor's Total Earnings on the project from the NTP until the most recent Monthly Progress Meeting. This report shall reflect the Earnings of specific activities based on the agreements made in the field and approved between the Contractor and Contracting Officer at the most recent Monthly Progress Meeting. Provided that the Contractor has provided a complete schedule update, this report shall serve as the basis of determining Contractor Payment. Activities shall be grouped by bid item and sorted by activity numbers. This report shall: sum all activities in a bid item and provide a bid item percent; and complete and sum all bid items to provide a total project percent complete. The printed report shall contain, for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Total Quantity, Quantity to Date, Percent Complete (based on cost), and Earnings to Date.

3.5.5 Network Diagram

The network diagram shall be required on the initial schedule submission and on monthly schedule update submissions. The network diagram shall

01 32 01.00 10 -9 depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.5.1 Continuous Flow

Diagrams shall show a continuous flow from left to right with no arrows from right to left. The activity number, description, duration, and estimated earned value shall be shown on the diagram.

3.5.5.2 Project Milestone Dates

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

3.5.5.3 Critical Path

The critical path shall be clearly shown.

3.5.5.4 Banding

Activities shall be grouped to assist in the understanding of the activity sequence. Typically, this flow will group activities by category of work, work area and/or responsibility.

3.5.5.5 S-Curves

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

3.6 PERIODIC PROGRESS MEETINGS

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

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

3.6.1 Meeting Attendance

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

3.6.2 Update Submission Following Progress Meeting

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

3.6.3 Progress Meeting Contents

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

01 32 01.00 10 -10

3.6.3.1 Start and Finish Dates

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

3.6.3.2 Time Completion

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

3.6.3.3 Cost Completion

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

3.6.3.4 Logic Changes

All logic changes pertaining to NTP on change orders, change orders to be incorporated into the schedule, contractor proposed changes in work sequence, corrections to schedule logic for out-of-sequence progress, lag durations, and other changes that have been made pursuant to contract provisions shall be specifically identified and discussed.

3.6.3.5 Other Changes

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

3.7 REQUESTS FOR TIME EXTENSIONS

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

3.7.1 Justification of Delay

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

01 32 01.00 10 -11

3.7.2 Submission Requirements

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

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

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

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

d. A sub-network of the affected area.

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

3.7.3 Additional Submission Requirements

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

3.8 DIRECTED CHANGES

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

3.9 OWNERSHIP OF FLOAT

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

-- End of Section --

01 32 01.00 10 -12

Section 01 35 26 Page 1

SECTION 01 35 26

GOVERNMENTAL SAFETY REQUIREMENTS

02/12

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.

AMERICAN SOCIETY OF SAFETY ENGINEERS (ASSE/SAFE)

ASSE/SAFE A10.34 (2001; R 2012) Protection of the Public on or

Adjacent to Construction Sites

ASME INTERNATIONAL (ASME)

ASME B30.22 (2010) Articulating Boom Cranes

ASME B30.3 (2012) Tower Cranes

ASME B30.5 (2011) Mobile and Locomotive Cranes

CALIFORNIA CODE OF REGULATIONS (CCR)

8 CCR 1509 Title 8, Section 1509 Injury and Illness

Prevention Program

8 CCR 3203 Title 8, Section 3203 Injury and Illness

Prevention Program

8 CCR 5144 Title 8, Section 5144 Respiratory Protection

8 CCR 5194 Title 8, Section 5194, Hazard Communication

8 CCR Ch 4 Subch 4 Title 8, Chapter 4, Subchapter 4, Construction Safety Orders

8 CCR Ch 4 Subch 7 Title 8, Chapter 4, Subchapter 7, General

Industry Safety Orders

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 10 (2013) Standard for Portable Fire

Extinguishers

NFPA 51B (2014) Standard for Fire Prevention During

Welding, Cutting, and Other Hot Work

NFPA 70E (2012; Errata 2012) Standard for Electrical

Safety in the Workplace

U.S. ARMY CORPS OF ENGINEERS (USACE)

Section 01 35 26 Page 2

EM 385-1-1 (2008; Errata 1-2010; Changes 1-3 2010;

Changes 4-6 2011; Change 7 2012) Safety and Health Requirements Manual

U.S. NATIONAL ARCHIVES AND RECORDS ADMINISTRATION (NARA)

10 CFR 20 Standards for Protection Against Radiation

29 CFR 1910 Occupational Safety and Health Standards

29 CFR 1910.146 Permit-required Confined Spaces

29 CFR 1926 Safety and Health Regulations for

Construction

29 CFR 1926.1400 Cranes & Derricks in Construction

29 CFR 1926.16 Rules of Construction

CPL 2.100 (1995) Application of the Permit-Required

Confined Spaces (PRCS) Standards, 29 CFR 1910.146

1.2 DEFINITIONS

a. High Visibility Accident. Any mishap which may generate publicity or high visibility.

b. Medical Treatment. Treatment administered by a physician or by registered professional personnel under the standing orders of a physician. Medical treatment does not include first aid treatment even through provided by a physician or registered personnel.

c. Recordable Injuries or Illnesses. Any work-related injury or illness that results in:

(1) Death, regardless of the time between the injury and death, or the length of the illness;

(2) Days away from work (any time lost after day of injury/illness onset);

(3) Restricted work;

(4) Transfer to another job;

(5) Medical treatment beyond first aid;

(6) Loss of consciousness; or

(7) A significant injury or illness diagnosed by a physician or other licensed health care professional, even if it did not result in (1) through (6) above.

d. "USACE" property and equipment specified in USACE EM 385-1-1 should be interpreted as Government property and equipment.

Section 01 35 26 Page 3

e. Weight Handling Equipment (WHE) Accident. A WHE accident occurs when any one or more of the eight elements in the operating envelope fails to perform correctly during operation, including operation during maintenance or testing resulting in personnel injury or death; material or equipment damage; dropped load; derailment; two-blocking; overload;

or collision, including unplanned contact between the load, crane, or other objects. A dropped load, derailment, two-blocking, overload and collision are considered accidents even though no material damage or injury occurs. A component failure (e.g., motor burnout, gear tooth failure, bearing failure) is not considered an accident solely due to material or equipment damage unless the component failure results in damage to other components (e.g., dropped boom, dropped load, roll over, etc.) Any mishap meeting the criteria described above shall be documented in both the Contractor Significant Incident Report (CSIR) submitted within five days both as provided by the Contracting Officer.

1.3 SUBMITTALS

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

submittals not having a "G" designation are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Accident Prevention Plan (APP); G, A

Activity Hazard Analysis (AHA); G, A

Crane Critical Lift Plan; G, A

Proof of qualification for Crane Operators; G, A

SD-06 Test Reports

Notifications and Reports

Submit reports as their incidence occurs, in accordance with the requirements of the paragraph, "Notifications and Reports"

Accident Investigation Reports

Crane Reports

SD-07 Certificates

Confined Space Entry Permit

Hot work permit

License Certificates

1.4 REGULATORY REQUIREMENTS

In addition to the detailed requirements included in the provisions of this contract, comply with the most recent addition of USACE EM 385-1-1, and all

Section 01 35 26 Page 4 applicable federal, Air Force, state, and local laws, ordinances, criteria, rules and regulations including 8 CCR Ch 4 Subch 4, 8 CCR Ch 4 Subch 7, 8 CCR 3203, 8 CCR 1509, 8 CCR 5144, and 8 CCR 5194. Submit matters of interpretation of standards to the appropriate administrative agency for resolution before starting work. Where the requirements of this specification, applicable laws, criteria, ordinances, regulations, and referenced documents vary, the most stringent requirements govern.

1.5 SITE QUALIFICATIONS, DUTIES AND MEETINGS

1.5.1 Personnel Qualifications

1.5.1.1 Site Safety and Health Officer (SSHO)

The SSHO must meet the requirements of EM 385-1-1 section 1 and ensure that the requirements of 29 CFR 1926.16 are met for the project. Provide a Safety oversight team that includes a minimum of one (1) person at each project site to function as the Site Safety and Health Officer (SSHO). The SSHO or alternate SSHO shall be at the work site at all times to implement and administer the Contractor's safety program and government-accepted Accident Prevention Plan. The SSHO's training, experience, and qualifications shall be as required by EM 385-1-1 paragraph 01.A.17, entitled SITE SAFETY AND HEALTH OFFICER (SSHO), and all associated sub-paragraphs. Full time SSHO is required for this project and shall have no other duties.

A Competent Person shall be provided for all of the hazards identified in the Contractor's Safety and Health Program in accordance with the accepted Accident Prevention Plan, and shall be on-site at all times when the work that presents the hazards associated with their professional expertise is being performed. Provide the credentials of the Competent Persons(s) to the Contracting Officer for acceptance in consultation with the Safety Office.

1.5.1.2 Crane Operators

Meet the crane operators requirements in USACE EM 385-1-1, Section 15 & 16 .

In addition, for mobile cranes with Original Equipment Manufacturer (OEM) rated capacitates of 50,000 pounds or greater, designate crane operators as qualified by a source that qualifies crane operators (i.e., union, a government agency, or an organization that tests and qualifies crane operators). Provide proof of current qualification.

1.5.2 Personnel Duties

1.5.2.1 Site Safety and Health Officer (SSHO)

The SSHO shall:

a. Conduct daily safety and health inspections and maintain a written log which includes area/operation inspected, date of inspection, identified hazards, recommended corrective actions, estimated and actual dates of corrections. Attach safety inspection logs to the Contractors' daily quality control report.

b. Conduct mishap investigations and complete required reports. Maintain the OSHA Form 300 and 301.

Section 01 35 26 Page 5

c. Maintain applicable safety reference material on the job site.

d. Attend the pre-construction conference, pre-work meetings including preparatory inspection meeting, and periodic in-progress meetings.

e. Implement and enforce accepted APPS and AHAs. Perform periodic evaluation of the APP & AHA to ensure they are reflective of work being done.

f. Maintain a safety and health deficiency tracking system that monitors outstanding deficiencies until resolution. Post a list of unresolved safety and health deficiencies on the safety bulletin board.

g. Shall be empowered to stop work when necessary and ensure sub-contractor compliance with safety and health requirements.

h. Maintain a list of hazardous chemicals on site and their material safety data sheets.

Failure to perform the above duties will result in dismissal of the superintendent, QC Manager, and/or SSHO, and a project work stoppage.

The project work stoppage will remain in effect pending approval of a suitable replacement.

1.5.3 Meetings

1.5.3.1 Preconstruction Conference

a. Contractor representatives who have a responsibility or significant role in accident prevention on the project shall attend the preconstruction conference. This includes the project superintendent, site safety and health officer, alternate SSHO, quality control supervisor, or any other assigned safety and health professionals who participated in the development of the APP (including the Activity Hazard Analyses (AHAs) and special plans, program and procedures associated with it).

b. Discuss the details of the submitted APP to include incorporated plans, programs, procedures and a listing of anticipated AHAs that will be developed and implemented during the performance of the contract. This list of proposed AHAs will be reviewed at the conference and an agreement will be reached between the Contractor and the Contracting Officer's representative as to which phases will require an analysis.

In addition, establish a schedule for the preparation, submittal, review, and acceptance of AHAs to preclude project delays.

c. Deficiencies in the submitted APP will be brought to the attention of the Contractor at the preconstruction conference, and the Contractor shall revise the plan to correct deficiencies and re-submit it for acceptance. Work shall not begin until there is an accepted APP.

d. The functions of a Preconstruction conference may take place at the

Post-Award Kickoff meeting for Design Build Contracts.

1.6 ACCIDENT PREVENTION PLAN (APP)

Section 01 35 26 Page 6

Use a qualified person to prepare the written site-specific APP. Prepare the APP in accordance with the format and requirements of USACE EM 385-1-1 and as supplemented herein. Cover all paragraph and subparagraph elements in USACE EM 385-1-1, Appendix A, "Minimum Basic Outline for Accident Prevention Plan". Specific requirements for some of the APP elements are described below. The APP shall be job-specific and address any unusual or unique aspects of the project or activity for which it is written. The APP shall interface with the Contractor's overall safety and health program. Include any portions of the Contractor's overall safety and health program referenced in the APP in the applicable APP element and made site-specific.

The Government considers the Prime Contractor to be the "controlling authority" for all work site safety and health of the subcontractors.

Contractors are responsible for informing their subcontractors of the safety provisions under the terms of the contract and the penalties for noncompliance, coordinating the work to prevent one craft from interfering with or creating hazardous working conditions for other crafts, and inspecting subcontractor operations to ensure that accident prevention responsibilities are being carried out. The APP shall be signed by the person and firm (senior person) preparing the APP, the Contractor, the on-site superintendent, the designated site safety and health officer, the Contractor Quality control Manager, and any designated CSP or CIH.

Submit the APP to the Contracting Officer 15 calendar days prior to the date of the preconstruction conference for acceptance. Work cannot proceed without an accepted APP.

Once accepted by the Contracting Officer, the APP and attachments will be enforced as part of the contract. Disregarding the provisions of this contract or the accepted APP will be cause for stopping of work, at the discretion of the Contracting Officer, until the matter has been rectified.

Once work begins, changes to the accepted APP shall be made with the knowledge and concurrence of the Contracting Officer, project superintendent, SSHO and quality control manager. Should any severe hazard exposure, i.e. imminent danger, become evident, stop work in the area, secure the area, and develop a plan to remove the exposure and control the hazard. Notify the Contracting Officer within 24 hours of discovery.

Eliminate/remove the hazard. In the interim, take all necessary action to restore and maintain safe working conditions in order to safeguard onsite personnel, visitors, the public (as defined by ASSE/SAFE A10.34,) and the environment.

Copies of the accepted plan will be maintained at the resident engineer's office and at the job site. Continuously review and amend the APP, as necessary, throughout the life of the contract. Incorporate unusual or high-hazard activities not identified in the original APP as they are discovered.

1.6.1 EM 385-1-1 Contents

In addition to the requirements outlined in Appendix A of USACE EM 385-1-1, the following is required:

a. Crane Critical Lift Plan.

Prepare and sign weight handling critical lift plans for lifts over 75 percent of the capacity of the crane or hoist (or lifts over 50 percent of the capacity of a barge mounted mobile crane's hoists) at any radius of

Section 01 35 26 Page 7 lift; lifts involving more than one crane or hoist; lifts of personnel; and lifts involving non-routine rigging or operation, sensitive equipment, or unusual safety risks. Submit 15 calendar days prior to on-site work and include the requirements of USACE EM 385-1-1, paragraph 16.H. and the following:

(1) For lifts of personnel, demonstrate compliance with the requirements of

29 CFR 1926.1400.

b. Site Demolition Plan. The safety and health aspects prepared in accordance with Section 02 41 00 DECONSTRUCTION and referenced sources.

Include engineering survey as applicable.

c. Excavation Plan. The safety and health aspects prepared in accordance with Section 31 00 00 EARTHWORK and EM 385-1-1 Section 25. Ensure areas involved are cleared for UXO/MEC before doing any excavations.

1.7 ACTIVITY HAZARD ANALYSIS (AHA)

The Activity Hazard Analysis (AHA) format shall be in accordance with USACE EM 385-1-1, Section 1. Submit the AHA for review at least 15 calendar days prior to the start of each phase. Format subsequent AHAs as amendments to the APP. The analysis should be used during daily inspections to ensure the implementation and effectiveness of the activity's safety and health controls.

The AHA list will be reviewed periodically (at least monthly) at the Contractor supervisory safety meeting and updated as necessary when procedures, scheduling, or hazards change.

Develop the activity hazard analyses using the project schedule as the basis for the activities performed. Any activities presenting hazards on the project schedule will require an AHA. The AHAs will be developed by the contractor, supplier or subcontractor and provided to the prime contractor for submittal to the Contracting Officer.

1.8 DISPLAY OF SAFETY INFORMATION

Within one calendar day(s) after commencement of work, erect a safety bulletin board at the job site. Where size, duration, or logistics of project do not facilitate a bulletin board, an alternative method, acceptable to the Contracting Officer, that is accessible and includes all mandatory information for employee and visitor review, shall be deemed as meeting the requirement for a bulletin board. Include and maintain information on safety bulletin board as required by EM 385-1-1, section 01.A.06. Additional items required to be posted include:

a. Confined space entry permit.

b. Hot work permit.

1.9 SITE SAFETY REFERENCE MATERIALS

Maintain safety-related references applicable to the project, including those listed in the article "References." Maintain applicable equipment manufacturer's manuals.

Section 01 35 26 Page 8

1.10 EMERGENCY MEDICAL TREATMENT

Contractors will arrange for their own emergency medical treatment.

Government has no responsibility to provide emergency medical treatment.

1.11 NOTIFICATIONS AND REPORTS

1.11.1 Accident Notification

Notify the Contracting Officer as soon as practical, but no more than four hours after any accident meeting the definition of Recordable Injuries or Illnesses or High Visibility Accidents, property damage equal to or greater than $2,000, or any weight handling equipment accident. Within notification include contractor name; contract title; type of contract; name of activity, installation or location where accident occurred; date and time of accident;

names of personnel injured; extent of property damage, if any; extent of injury, if known, and brief description of accident (to include type of construction equipment used, PPE used, etc.)using SPK Form 385-1-R.

Preserve the conditions and evidence on the accident site until the Government investigation team arrives on-site and Government investigation is conducted.

1.11.2 Accident Investigation Reports

a. Conduct an accident investigation for recordable injuries and illnesses, for Medical Treatment defined in paragraph DEFINITIONS, property damage accidents resulting in at least $20,000 in damages, and near misses as defined in EM 385-1-1, to establish the root cause(s) of the accident. Complete the applicable USACE Accident Investigation Report Form 3394, and provide the report to the Contracting Officer within 5 calendar day(s) of the accident. The Contracting Officer will provide copies of any required or special forms.

b. Conduct an accident investigation for any weight handling equipment accident (including rigging gear accidents) to establish the root cause(s) of the accident, complete the WHE Accident Report (Crane and Rigging Gear) form and provide the report to the Contracting Officer within 30 calendar days of the accident. Do not proceed with crane operations until cause is determined and corrective actions have been implemented to the satisfaction of the contracting officer. The Contracting Officer will provide a blank copy of the accident report form.

1.11.3 Crane Reports

Submit crane inspection reports required in accordance with USACE EM 385-1- 1, Appendix I and as specified herein with Daily Reports of Inspections.

1.12 HOT WORK

Submit and obtain a written permit prior to performing "Hot Work" (welding, cutting, etc.) or operating other flame-producing/spark producing devices, from the Fire Division. A permit is required from the Base Explosives Safety Office for work in and around where explosives are processed, stored, or handled. CONTRACTORS ARE REQUIRED TO MEET ALL CRITERIA BEFORE A PERMIT IS ISSUED. Provide at least two (2) twenty (20) pound 4A:20 BC rated extinguishers for normal "Hot Work". All extinguishers shall be current

Section 01 35 26 Page 9 inspection tagged, approved safety pin and tamper resistant seal. It is also mandatory to have a designated FIRE WATCH for any "Hot Work" done at this activity. The Fire Watch shall be trained in accordance with NFPA 51B and remain on-site for a minimum of 60 minutes after completion of the task or longer as specified on the hot work permit.

When starting work in the facility, require personnel to familiarize themselves with the location of the nearest fire alarm boxes and place in memory the emergency Fire Division phone number. ANY FIRE, NO MATTER HOW

SMALL, SHALL BE REPORTED TO THE RESPONSIBLE FIRE DIVISION IMMEDIATELY.

1.13 RADIATION SAFETY REQUIREMENTS

License Certificates for radiation materials and equipment shall be submitted to the Contracting Officer and Base Radiation Safety Office (RSO)for all specialized and licensed material and equipment that could cause fatal harm to construction personnel or to the construction project.

Workers shall be protected from radiation exposure in accordance with 10 CFR 20 Standards for Protection Against Radiation

Loss of radioactive material shall be reported immediately to the Contracting Officer and base RSO.

1.14 FACILITY OCCUPANCY CLOSURE

Streets, walks, and other facilities occupied and used by the Government shall not be closed or obstructed without written permission from the Contracting Officer.

1.15 SEVERE STORM PLAN

In the event of a severe storm warning, the Contractor must:

a. Secure outside equipment and materials and place materials that could be damaged in protected areas.

b. Check surrounding area, including roof, for loose material, equipment, debris, and other objects that could be blown away or against existing facilities.

c. Ensure that temporary erosion controls are adequate.

1.16 CONFINED SPACE ENTRY REQUIREMENTS.

Contractors entering and working in confined spaces while performing general industry work are required to follow the requirements of OSHA 29 CFR 1926 and comply with the requirements in Section 34 of EM 385-1-1, OSHA 29 CFR 1910, and OSHA 29 CFR 1910.146.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Section 01 35 26 Page 10

3.1 CONSTRUCTION AND OTHER WORK

3.1.1 Hazardous Material Exclusions

Notwithstanding any other hazardous material used in this contract, radioactive materials or instruments capable of producing ionizing/non-ionizing radiation (with the exception of radioactive material and devices used in accordance with USACE EM 385-1-1 such as nuclear density meters for compaction testing and laboratory equipment with radioactive sources) as well as materials which contain asbestos, mercury polychlorinated biphenyls, di-isocynates, hexavalent chromium, or lead-based paint are prohibited. The Contracting Officer, upon written request by the Contractor, may consider exceptions to the use of any of the above excluded materials. Low mercury lamps used within fluorescent lighting fixtures are allowed as an exception without further Contracting Officer approval.

Notify the Radiation Safety Officer (RSO) prior to excepted items of radioactive material and devices being brought on base.

3.1.2 Unforeseen Hazardous Material

The design should have identified materials such as PCB, lead paint, and friable and non-friable asbestos and other OSHA regulated chemicals (i.e. 29 CFR Part 1910.1000). If additional material, not indicated, that may be hazardous to human health upon disturbance during construction operations is encountered, stop that portion of work and notify the Contracting Officer immediately. Within 14 calendar days the Government will determine if the material is hazardous. If material is not hazardous or poses no danger, the Government will direct the Contractor to proceed without change. If material is hazardous and handling of the material is necessary to accomplish the work, the Government will issue a modification pursuant to "FAR 52.243-4, Changes" and "FAR 52.236-2, Differing Site Conditions."

3.2 PRE-OUTAGE COORDINATION MEETING

Apply for utility outages at least 15 days in advance. As a minimum, the request should include the location of the outage, utilities being affected, duration of outage and any necessary sketches. Special requirements for electrical outage requests are contained elsewhere in this specification section. Once approved, and prior to beginning work on the utility system requiring shut down, attend a pre-outage coordination meeting with the Contracting Officer and the Installation representative to review the scope of work and the lock-out/tag-out procedures for worker protection.