YAQF082005 WIANG Upgrade B503 B2 Specs.pdf
PDF 11 MB Posted
- Solicitation number
- W912J2-22-B-0001
About this file
This document provides details for an invitation for bids to upgrade building 504 fire detection and install fire suppression at Volk Field Air National Guard Base in Camp Douglas, Wisconsin. The solicitation seeks a single firm fixed-price contract for plans, labor, materials, equipment, and supervision to complete project YAQF082005. Specific requirements include upgrading the fire detection system and installing a fire suppression system. The North American Industry Classification code is 236220 for commercial and institutional buildings, with a size standard of $39.5 million average annual revenue. The contract period is 365 days from notice to proceed, with a project magnitude between $1 million to $5 million. Interested parties must register in the System for Award Management and attend a pre-bid conference on specified dates. Bids are due by the closing date listed in the solicitation, and funds are expected to be available by September 30, 2022. The award will be made to the responsive and responsible lowest bidder.
View the file
Other files
Show all 20
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
TYPE B-2 (PRE-FINAL) SUBMITTAL
SPECIFICATIONS
UPGRADE BUILDING 504 FIRE DETECTION,
INSTALL FIRE SUPPRESSION
Volk Field ANGB, Camp Douglas, WI
YAQF082005
W912J2-22-F-0022
FA8903-21-D-0012
Prepared For:
Prepared By:
3500 Parkway Lane, Suite 500
Peachtree Corners, Georgia 30092 678.336.7740 www.pondco.com
15 July 2022 Project No. 1220390
Volk Field CRTC
1000 Independence Drive
Camp Douglas, WI 54618
WIANG Upgrade Bldg 504 YAQF082005 Fire Detection & Install Fire Suppression Type B2 Pre-Final
THIS PAGE INTENTIONALLY LEFT BLANK
WIANG Upgrade Bldg 504
Fire Detection & Install Fire Suppression
YAQF082005
Type B2 Pre-Final
PROJECT TABLE OF CONTENTS Page 1
PROJECT TABLE OF CONTENTS
DIVISION 01 - GENERAL REQUIREMENTS
01 11 00 SUMMARY OF WORK
01 14 00 WORK RESTRICTIONS
01 20 00 PRICE AND PAYMENT PROCEDURES
01 30 00 ADMINISTRATIVE REQUIREMENTS
01 32 01.00 10 PROJECT SCHEDULE
01 33 00 SUBMITTAL PROCEDURES
01 33 00A SUBMITTAL REGISTER
01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS
01 42 00 SOURCES FOR REFERENCE PUBLICATIONS
01 45 00.00 10 QUALITY CONTROL
01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS
01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS
01 74 19 CONSTRUCTION WASTE MANAGEMENT AND DISPOSAL
01 75 00.00 40 STARTING AND ADJUSTING
01 78 00 CLOSEOUT SUBMITTALS
01 78 23 OPERATION AND MAINTENANCE DATA
DIVISION 02 - EXISTING CONDITIONS
02 41 00 DEMOLITION
DIVISION 03 - CONCRETE
03 30 00 CAST-IN-PLACE CONCRETE
DIVISION 04 - MASONRY
04 20 00 UNIT MASONRY
DIVISION 05 - METALS
05 12 00 STRUCTURAL STEEL
05 21 00 STEEL JOIST FRAMING
05 30 00 STEEL DECKS
DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES
06 10 00 ROUGH CARPENTRY
DIVISION 07 - THERMAL AND MOISTURE PROTECTION
07 21 13 BOARD AND BLOCK INSULATION
07 22 00 ROOF AND DECK INSULATION
07 24 00 EXTERIOR INSULATION AND FINISH SYSTEMS
07 41 13 METAL ROOF PANELS
07 60 00 FLASHING AND SHEET METAL
07 84 00 FIRESTOPPING
07 92 00 JOINT SEALANTS
DIVISION 08 - OPENINGS
08 11 13 STEEL DOORS AND FRAMES
08 71 00 DOOR HARDWARE
DIVISION 09 - FINISHES
WIANG Upgrade Bldg 504
Fire Detection & Install Fire Suppression
YAQF082005
Type B2 Pre-Final
PROJECT TABLE OF CONTENTS Page 2
09 67 23.16 FUEL RESISTIVE RESINOUS FLOORING, 5-COAT SYSTEM
09 90 00 PAINTS AND COATINGS
DIVISION 21 - FIRE SUPPRESSION
21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION
21 13 18 PREACTION SPRINKLER SYSTEMS, FIRE PROTECTION
21 30 00 FIRE PUMPS
DIVISION 22 - PLUMBING
22 14 29.00 40 SUMP PUMPS
DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING (HVAC)
23 00 00 AIR SUPPLY, DISTRIBUTION, VENTILATION, AND EXHAUST SYSTEMS
23 05 15 COMMON PIPING FOR HVAC
23 82 46.00 40 ELECTRIC UNIT HEATERS
DIVISION 26 - ELECTRICAL
26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS
26 12 19.10 THREE-PHASE PAD-MOUNTED TRANSFORMERS
26 20 00 INTERIOR DISTRIBUTION SYSTEM
26 24 13 SWITCHBOARDS
26 51 00 INTERIOR LIGHTING
DIVISION 28 - ELECTRONIC SAFETY AND SECURITY
28 31 64.00 10 FIRE DETECTION AND ALARM SYSTEM, ADDRESSABLE
DIVISION 31 - EARTHWORK
31 00 00 EARTHWORK
31 31 16.13 CHEMICAL TERMITE CONTROL
DIVISION 32 - EXTERIOR IMPROVEMENTS
32 01 19 FIELD MOLDED SEALANTS FOR SEALING JOINTS IN RIGID PAVEMENTS
32 11 20 BASE COURSE FOR RIGID PAVING
32 12 16 HOT-MIX ASPHALT (HMA) FOR ROADS
32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE
FACILITIES
32 92 19 SEEDING
DIVISION 33 - UTILITIES
33 11 00 WATER UTILITY DISTRIBUTION PIPING
33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION
ATTACHMENTS
ATTACHMENT A GEOTECHNICAL ENGINEERING REPORT
ATTACHMENT B LEAD AND ASBESTOS REPORT
ATTACHMENT C REGULATED MATERIALS SURVEY REPORT
-- End of Project Table of Contents --
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. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit in accordance with Section 01 33 00 SUBMITTAL PROCEDURES.
1.2 WORK COVERED BY CONTRACT DOCUMENTS
1.2.1 Project Description
The work includes furnishing all plant, equipment, labor, devices, tools, materials, transportation, services, supervision and all miscellaneous requirements to perform all operations in conjunction with the efforts to accomplish the work. Work includes the construction and installation of a fire suppression and fire detection system in the existing Hangar Building 504 at Volk Field Air National Guard Base. Site work is included. All work shall be complete and function as intended, as if identified exclusively.
All work shall be accomplished in accordance with applicable drawings, specifications, industry standards, applicable Building and Environmental Codes, Regulations, and Laws. Project elements include, but are not limited to: sitework, utilities, water storage tank, HVAC systems, plumbing, power, lighting and the addition of a approx 264 SF fire pump room. Contractor shall comply with all applicable Unified Facilities Criteria (UFC) and Air National Guard Engineering Technical Letters (ANG ETL) in addition to Federal, State and local requirements, and obtain any required permits.
The Hangar will be occupied and operational during construction.
Contractor shall schedule activities so as to minimize the down-time of the Hangar. Extended hours and weekend work may, at the discretion of the Government, be approved to minimize impacts. See 01 14 00, paragraphs
1.2.2 and 1.2.3.
1.2.2 Location
The work is located at Volk Field Air National Guard Base, Camp Douglas, Wisconsin. The exact location will be shown by the Contracting Officer.
1.3 EXISTING WORK
In addition to "FAR 52.236-9, Protection of Existing Vegetation, Structures, Equipment, Utilities, and Improvements":
a. Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work which remain.
b. Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer. At the completion of operations, SECTION 01 11 00 Page 1 existing work must be in a condition equal to or better than that which existed before new work started.
1.4 LOCATION OF UNDERGROUND UTILITIES
Obtain digging and utility permits prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities. Verify existing utility locations indicated on contract drawings, within area of work.
1.4.1 Notification Prior to Excavation
Notify the Contracting Officer at least 72 hours prior to starting excavation work.
1.5 SALVAGE MATERIAL AND EQUIPMENT
Items designated by the Contracting Officer to be salvaged remain the property of the Government. Segregate, itemize, deliver and off-load the salvaged property at the Government designated storage area located within 3 miles of the construction site.
1.6 CONTRACTOR MANPOWER REPORTING
The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Army collection site. The contractor is required to completely fill in all required data fields using the following web address: https://cmra.army.mil/. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30.
While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk at https://cmra.army.mil/.
PART 2 PRODUCTS
Not used.
PART 3 EXECUTION
Not used.
-- End of Section --
SECTION 01 11 00 Page 2
SECTION 01 14 00
WORK RESTRICTIONS
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. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:
SD-01 Preconstruction Submittals
List of Contact Personnel ; G
1.2 CONTRACTOR ACCESS AND USE OF PREMISES
1.2.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.2.1.1 Subcontractors and Personnel Contacts
Provide a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.
1.2.1.2 Identification Badges and Installation Access
Application for and use of badges will be as directed. Obtain access to the installation by participating in the Defense Biometric Identification System (DBIDS) , or by obtaining passes each day from the Base Pass and Identification Office. Costs for obtaining passes through the DBIDS are the responsibility of the Contractor. One-day passes, issued through the Base Pass and Identification Office, will be furnished without charge.
Furnish a completed EMPLOYMENT ELIGIBILITY VERIFICATION (DHS FORM I-9) form for all personnel requesting badges. This form is available at http://www.uscis.gov/portal/site/uscis by searching or selecting Employment Verification (Form I-9). Immediately report instances of lost or stolen badges to the Contracting Officer. A Federal ID is required.
a. DBIDS Program: The Defense Biometric Identification System (DBIDS) is a Department of Defense (DoD) system developed by DMDC as a force protection program to manage personnel, property and installation access. It is a networked client/server database system designed to easily verify the access authorization of personnel entering military installations by the use of barcode technology and fingerprint
SECTION 01 14 00 Page 1 biometric identification. The DBIDS software application is used to enter personnel data into a database, capture biometric information, and retrieve that data and biometric information for verification and validation at a later time. The program supports the adding, retrieving, updating, and displaying of information for individuals, who require military installation access. The program alerts registration personnel and installation gate guards to barred individuals across jurisdictional boundaries, and eliminates duplication of data.
b. One-Day Passes: Participation in the DBIDS is not mandatory, and if the Contractor chooses to not participate, the Contractor's personnel will have to obtain daily passes, be subject to daily mandatory vehicle inspection, and will have limited access to the installation.
The Government will not be responsible for any cost or lost time associated with obtaining daily passes or added vehicle inspections incurred by non-participants in the DBIDS.
c. ACCESS AND GENERAL PROTECTION/SECURITY POLICY & PROCEDURES
The contractor shall comply with all applicable installation/facility access and local security policies and procedures, which may be obtained from the Contracting Officer's Representative (COR). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by the local installation's Security Forces, Director of Emergency Services or local Security Office. The contractor shall ensure compliance with all personal identity verification requirements as directed by DoD, HAF and/or local policy. Should the Force Protection Condition (FPCON) change, the Government may require changes in contractor security matters or processes.
Contractor and all associated sub?contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (AFI 31-101 and AFI 10-245), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.
1.2.1.3 No Smoking Policy
Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.
1.2.2 Working Hours
Regular working hours must consist of an 9 period, between 7 a.m. and 4 p.m., Monday through Friday, excluding Government holidays.
1.2.3 Work Outside Regular Hours
Work outside regular working hours requires Contracting Officer approval.
SECTION 01 14 00 Page 2
Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title. Based on the justification provided, the Contracting Officer may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer.
1.2.4 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 the paragraph "Work Outside Regular Hours."
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, compressed air, are considered utility cutovers pursuant to the paragraph entitled "Work Outside Regular Hours."
d. Operation of Base Utilities: The Contractor must not operate nor disturb the setting of control devices in the base 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 giving reasonable advance notice when such operation is required.
1.2.5 AT Level 1 Training
All contractor employees, include subcontractor employees, requiring access Government installations, Facilities and Controlled Access areas shall complete AT Level I awareness training within 20 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. Certificates of completion for each affected contractor employee and subcontractor employee will be maintained by the COR or Antiterrorism Representative. AT level I Awareness Training is available at the following website:
http://jko.jten.mil.
PART 2 PRODUCTS
Not Used
PART 3 EXECUTION
Not Used
SECTION 01 14 00 Page 3
SECTION 01 14 00 Page 4
SECTION 01 20 00
PRICE AND PAYMENT PROCEDURES
PART 1 GENERAL
1.1 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:
1.2 CONTRACTOR'S INVOICE AND CONTRACT PERFORMANCE STATEMENT
1.2.1 Submission of Invoices
If DFARS Clause 252.232-7006 Wide Area WorkFlow Payment Instructions is included in the Contract, provide the documents listed in above paragraph CONTENT OF INVOICE in their entirety as attachments in Wide Area Work Flow (WAWF) for each invoice submitted. The maximum size of each WAWF attachment is two megabytes, but there are no limits on the number of attachments. If a document cannot be attached in WAWF due to system or size restriction, provide it as instructed by the Contracting Officer.
Monthly invoices and supporting forms for work performed through the anniversary award date of the Contract must be submitted to the Contracting Officer within 5 calendar days of the date of invoice. For example, if Contract award date is the 7th of the month, the date of each monthly invoice must be the 7th and the invoice must be submitted by the 12th of the month.
1.2.2 Final Invoice
a. A final invoice must be accompanied by the certification required by DFARS 252.247.7023 Transportation of Supplies by Sea, and the Contractor's Final Release. If the Contractor is incorporated, the Final Release must contain the corporate seal. An officer of the corporation must sign and the corporate secretary must certify the Final Release.
b. For final invoices being submitted via WAWF, the original Contractor's Final Release Form and required certification of Transportation of Supplies by Sea must be provided directly to the respective Contracting Officer prior to submission of the final invoice. Once receipt of the original Final Release Form and required certification of Transportation of Supplies by Sea has been confirmed by the Contracting Officer, the Contractor must then submit final invoice and attach a copy of the Final Release Form and required certification of Transportation of Supplies by Sea in WAWF.
c. Final invoices not accompanied by the Contractor's Final Release and required certification of Transportation of Supplies by Sea will be considered incomplete and will be returned to the Contractor.
SECTION 01 20 00 Page 1
PART 2 PRODUCTS
Not Used
PART 3 EXECUTION
Not Used
SECTION 01 20 00 Page 2
SECTION 01 30 00
ADMINISTRATIVE REQUIREMENTS
PART 1 GENERAL
1.1 REFERENCES
The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.
U.S. ARMY CORPS OF ENGINEERS (USACE)
EM 385-1-1 (2014) Safety -- Safety and Health Requirements Manual
1.2 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:
SD-01 Preconstruction Submittals
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 from a minimum of ten different viewpoints selected by the Contractor unless otherwise directed by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures.
Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file.
Include a date designator in file names. 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, SECTION 01 30 00 Page 1 during the entire period of performance under this contract. Provide other insurance coverage as required by State of Wisconsin law .
1.6 SUPERVISION
1.6.1 Superintendent Qualifications
Provide project superintendent with a minimum of 10 years experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Contracting Officer may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.
For projects where the superintendent is permitted to also serve as the Quality Control (QC) Manager as established in Section 01 45 00.00 10 QUALITY CONTROL, the superintendent must have qualifications in accordance with that section.
1.6.2 Minimum Communication Requirements
Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of Contract work.In addition, if a Quality Control (QC) representative is required on the Contract, then that individual must also have fluent English communication skills.
1.6.3 Duties
The project superintendent is primarily responsible for managing subcontractors and coordinating day-to-day production and schedule adherence on the project. The superintendent is required to attend Red Zone meetings, partnering meetings, and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.
1.6.4 Non-Compliance Actions
The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to ensure timely completion.
Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.
1.7 PRECONSTRUCTION CONFERENCE
Immediately after award , prior to commencing any work at the site, coordinate with the Contracting Officer a time and place to meet for the Preconstruction Conference . The conference must take place within 35 calendar days after award of the contract, but prior to commencement of
SECTION 01 30 00 Page 2 any work at the site. The purpose of this conference is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to: daily reporting, invoicing, value engineering, safety, base-access, outage requests, hot work permits, schedule requirements, quality control, schedule of prices or earned value report, shop drawings, submittals, cybersecurity, prosecution of the work, government acceptance, final inspections and contract close-out.
Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.
1.7.1 Attendees
Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.
1.8 FACILITY TURNOVER PLANNING MEETINGS (Red Zone Meetings)
Meet with the Government to identify strategies to ensure the project is carried to expeditious closure and turnover to the Client. Start planning the turnover process at the Pre-Construction Conference with a discussion of the Red Zone process and convene at regularly scheduled Meetings beginning at approximately 75 percent of project completion. Include the following in the facility Turnover effort:
1.8.1 Red Zone Checklist
a. Contracting Officer's Technical Representative (COTR) will provide the Contractor a copy of the Red Zone Checklist template.
b. Prior to 75 percent completion, modify the Red Zone Checklist template by adding or deleting critical activities applicable to the project and assign planned completion dates for each activity. Submit the modified Red Zone Checklist to the Contracting Officer. The Contracting Officer may request additional activities be added to the Red Zone Checklist at any time as necessary.
1.8.2 Meetings
a. Conduct regular Red Zone Meetings beginning at approximately 75 percent project completion, or three to six months prior to Beneficial Occupancy Date (BOD), whichever comes first.
b. The Contracting Officer will establish the frequency of the meetings, which is expected to increase as the project completion draws nearer.
At the beginning, Red Zone meetings may be every two weeks then increase to weekly towards the final month of the project.
c. Using the Red Zone Checklist as a Plan of Action and Milestones (POAM) and basis for discussion, review upcoming critical activities and strategies to ensure work is completed on time.
d. During the Red Zone Meetings discuss with the COTR any upcoming activities that require Government involvement.
e. Maintain the Red Zone Checklist by documenting the actual completion dates as work is completed and update the Red Zone Checklist with revised planned completion dates as necessary to match progress.
Distribute copies of the current Red Zone Checklist to attendees at
SECTION 01 30 00 Page 3 each Red Zone Meeting.
1.9 PARTNERING
To most effectively accomplish this Contract, the Contractor and Government must form a cohesive partnership with the common goal of drawing on the strength of each organization in an effort to achieve a successful project without safety mishaps, conforming to the Contract, within budget and on schedule. The partnering team must consist of personnel from both the Government and Contractor including project level and corporate level leadership positions.
1.9.1 Team-Led (Informal) Partnering
a. The Contracting Officer will coordinate the initial Team-Led (Informal) Partnering Session with key personnel of the project team, including Contractor and Government personnel. The Partnering Session will be co-led by the Government Construction Manager and Contractor's Project Manager.
b. The Initial Team-led Partnering session may be held concurrently with the Pre-Construction Post-Award Kickoff meeting. Partnering sessions will be held at a location mutually agreed to by the Contracting Officer and the Contractor, typically at a conference room on-base or at the Contractor's temporary trailer.
c. The Initial Team-Led Partnering Session will be conducted and facilitated using electronic media (a video and accompanying forms) provided by Contracting Officer.
d. The Partners will determine the frequency of the follow-on sessions.
e. Participants will bear their own costs for meals, lodging and transportation associated with Partnering.
PART 2 PRODUCTS
Not Used
PART 3 EXECUTION
Not Used
SECTION 01 30 00 Page 4
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.
AACE INTERNATIONAL (AACE)
AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction
U.S. ARMY CORPS OF ENGINEERS (USACE)
ER 1-1-11 (1995) Administration -- Progress, Schedules, and Network Analysis Systems
1.2 SUBMITTALS
Government approval is required for submittals with a "G" designation;
submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:
SD-01 Preconstruction Submittals
Project Scheduler Qualifications ; G 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.
PART 2 PRODUCTS
2.1 SOFTWARE
The scheduling software utilized to produce and update the schedules required herein must be capable of meeting all requirements of this specification.
SECTION 01 32 01.00 10 Page 1
2.1.1 Contractor Software
2.1.1.1 Primavera
Government does not have access to Primavera. Provide PDF copies of the schedule.
PART 3 EXECUTION
3.1 GENERAL REQUIREMENTS
Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules.
Prepare each Project Schedule using the Precedence Diagram Method (PDM).
3.2 BASIS FOR PAYMENT AND COST LOADING
The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN.
3.2.1 Activity Cost Loading
Activity cost loading must be reasonable and without front-end loading.
Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.
3.2.2 Withholdings / Payment Rejection
Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.
In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.
3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS
3.3.1 Level of Detail Required
Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:
SECTION 01 32 01.00 10 Page 2
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 of mechanical/electrical/information systems layout drawings.
c. Long procurement activities
d. Submission and approval of O & M manuals.
e. Submission and approval of as-built drawings.
f . Submission and approval of DD1354 data and installed equipment lists.
g. Submission and approval of testing and air balance (TAB).
h. Other systems testing, if required.
i . Contractor's pre-final inspection.
j . Correction of punch list from Contractor's pre-final inspection.
k. Government's pre-final inspection.
l . Correction of punch list from Government's pre-final inspection.
m. Final inspection.
3.3.5 Government Activities
Show Government and other agency activities that could impact progress.
These activities include, but are not limited to: approvals, acceptance, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.
SECTION 01 32 01.00 10 Page 3
3.3.6 Standard Activity Coding Dictionary
Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 . This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site: http://rms.usace.army.mil .
The SDEF format is as follows:
Field Activity Code Length Description
1 WRKP 3 Workers per day
2 RESP 4 Responsible party
3 AREA 4 Area of work
4 MODF 6 Modification Number
5 BIDI 6 Bid Item (CLIN)
6 PHAS 2 Phase of work
7 CATW 1 Category of work
8 FOW 20 Feature of work*
*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the FEATURE OF WORK field requirements.
3.3.6.1 Workers Per Day (WRKP)
Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.
3.3.6.2 Responsible Party Coding (RESP)
Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.
a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.
b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record);
ELEC (for the electrical subcontractor); MECH (for the mechanical
SECTION 01 32 01.00 10 Page 4 subcontractor); and GOVT (for USACE).
3.3.6.3 Area of Work Coding (AREA)
Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew from working in more than one work area at a time due to restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings.
Activities cannot have more than one Work Area Code.
Not all activities are required to be Work Area coded. A lack of Work Area coding indicates the activity is not resource or space constrained.
3.3.6.4 Modification Number (MODF)
Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.
3.3.6.5 Bid Item Coding (BIDI)
Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code.
3.3.6.6 Phase of Work Coding (PHAS)
Assign Phase of Work Code to all activities. Examples of phase of work are procurement phase and construction phase. Each activity can have only one Phase of Work code.
a. Code proposed fast track design and construction phases proposed to allow filtering and organizing the schedule by fast track design and construction packages.
b. If the contract specifies phasing with separately defined performance periods, identify a Phase Code to allow filtering and organizing the schedule accordingly.
3.3.6.7 Category of Work Coding (CATW)
Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to construction submittals, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.
3.3.6.8 Feature of Work Coding (FOW)
Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan.
Definable Feature of Work is defined in Section 01 45 00.00 10 QUALITY
SECTION 01 32 01.00 10 Page 5
CONTROL. An activity can have only one Feature of Work Code.
3.3.7 Contract Milestones and Constraints
Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.
Mandatory constraints that ignore or effect network logic are prohibited.
No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.
3.3.7.1 Project Start Date Milestone and Constraint
The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged.
3.3.7.2 End Project Finish Milestone and Constraint
The last activity in the schedule must be a finish milestone titled "End Project."
Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.
3.3.7.3 Interim Completion Dates and Constraints
Constrain contractually specified interim completion dates to show negative float when the calculated late finish date of the last activity in that phase is later than the specified interim completion date.
3.3.7.3.1 Start Phase
Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work.
3.3.7.3.2 End Phase
Use a finish milestone as the last activity for a project phase. Call the finish milestone "End Phase X" where "X" refers to the phase of work.
3.3.8 Calendars
Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop sSeasonal Calendar(s) and assign to seasonally affected activities as applicable.
SECTION 01 32 01.00 10 Page 6
If an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated days provided in the contract clause TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends .
3.3.9 Open Ended Logic
Only two open ended activities are allowed: the first activity "NTP Acknowledged" may have no predecessor logic, and the last activity -"End Project" may have no successor logic.
Predecessor open ended logic may be allowed in a time impact analyses upon the Contracting Officer's approval.
3.3.10 Default Progress Data Disallowed
Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.
3.3.11 Out-of-Sequence Progress
Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer.
Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.
3.3.12 Added and Deleted Activities
Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.
3.3.13 Original Durations
Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.
3.3.14 Leads, Lags, and Start to Finish Relationships
Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb float, or to replace proper schedule logic.
SECTION 01 32 01.00 10 Page 7
a. Leads (negative lags) are prohibited.
b. Start to Finish (SF) relationships are prohibited.
3.3.15 Retained Logic
Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(s) starts and the predecessor activity(s) has not finished (out-of-sequence progress). Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") are not be allowed.
3.3.16 Percent Complete
Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management.
3.3.17 Remaining Duration
Update the remaining duration for each activity based on the number of estimated work days it will take to complete the activity. Remaining duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete.
3.3.18 Cost Loading of Closeout Activities
Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the present contract value. Activity(ies) may be declared 100 percent complete upon the Government's verification of completion and correction of all punch list work identified during Government pre-final inspection(s).
3.3.18.1 As-Built Drawings
If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than $35,000 or 1 percent of the present contract value, which ever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's approval.
3.3.18.2 O & M Manuals
Cost load the "Submission and approval of O & M manuals" activity not less than $20,000. Activity will be declared 100 percent complete upon the Government's approval of all O & M manuals.
3.3.19 Anticipated Adverse Weather
Paragraph applicable to contracts with clause entitled TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.
SECTION 01 32 01.00 10 Page 8
3.3.20 Early Completion Schedule and the Right to Finish Early
An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required contract work will be completed before the contractually required completion date.
a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.
b. The Government is under no obligation to accelerate work items it is responsible for to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.
3.4 PROJECT SCHEDULE SUBMISSIONS
Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.
Review comments made by the Government on the schedule(s) do not relieve the Contractor from compliance with requirements of the Contract Documents.
3.4.1 Preliminary Project Schedule Submission
Within 15 calendar days after the NTP is acknowledged submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).
3.4.2 Initial Project Schedule Submission
Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. No payment will be made for work items not fully detailed in the Project Schedule.
SECTION 01 32 01.00 10 Page 9
3.4.3 Periodic Schedule Updates
Update the Project Schedule on a regular basis, monthly at a minimum.
Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS. These updates will enable the Government to assess Contractor's progress.
a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.
b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.
3.5 SUBMISSION REQUIREMENTS
Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:
3.5.1 Data CD/DVDs
Provide two sets of data CD/DVDs containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include on the data CD/DVDs the Narrative Report and all required Schedule Reports. Label each CD/DVD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule must have a unique file name and use project specific settings.
3.5.2 Narrative Report
Provide a Narrative Report with each schedule submission. The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for any problems, either current or potential, which are revealed…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .