Specifications_Times_Square_Recruiting_Station_15_Jul_2016.pdf
PDF 3 MB Posted
- Attached to
- Renovations to Times Square Recruiting Booth
- Solicitation number
- W912DS-16-R-0014
About this file
W912DS-16-R-0014 SPECIFICATIONS
View the file
Other files
Show all 14
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
Times Square Recruiting Station Renovation Project
Times Square
New York, NY
PREPARED BY
GOSHOW A/E TEAM
Goshow Architects Architectural
EYP Engineering Structural, Mechanical, Plumbing, Electrical, Fire Alarm
GA Project Number: 201530 Contract Number: W1912DS-11-D-0001
July 15, 2016
SENSITIVE BUT UNCLASSIFIED (SBU)
Property of the United States Government. For Official Use Only. Do not remove this notice. Properly destroy or return documents when no longer needed
TIMES SQUARE RECRUITING STATION
PROJECT TABLE OF CONTENTS Page 1
PROJECT TABLE OF CONTENTS
DIVISION 00 – CONTRACTING REQUIREMENTS
00 01 15 LIST OF DRAWINGS
DIVISION 01 - GENERAL REQUIREMENTS
01 11 00 SUMMARY OF WORK
01 14 00 WORK RESTRICTIONS
01 32 01.00 10 PROJECT SCHEDULE
01 33 00 SUBMITTAL PROCEDURES
01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS
01 42 00 SOURCES FOR REFERENCE PUBLICATIONS
01 45 10.10 10 QUALITY CONTROL SYSTEM (QCS)
01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS
01 78 00 CLOSEOUT SUBMITTALS
01 78 23 OPERATION AND MAINTENANCE DATA
DIVISION 02 - EXISTING CONDITIONS
02 41 00 DEMOLITION AND DECONSTRUCTION
DIVISION 05 - METALS
05 50 13 MISCELLANEOUS METAL FABRICATIONS
DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES
06 10 00 ROUGH CARPENTRY
DIVISION 07 - THERMAL AND MOISTURE PROTECTION
07 01 50.19 PREPARATION FOR RE-ROOFING
07 21 16 MINERAL FIBER BLANKET INSULATION
07 54 19 POLYVINYL CHLORIDE (PVC) MEMBRANE ROOFING
07 60 00 FLASHING AND SHEET METAL
07 72 00 ROOF ACCESSORIES
07 76 16 ROOF DECKING PAVERS
07 92 00 JOINT SEALANTS
DIVISION 08 - OPENINGS
08 11 13 STEEL DOORS AND FRAMES
08 14 00 WOOD DOORS
08 31 13 ACCESS DOORS AND FRAMES
08 34 02 BULLET-RESISTANT COMPONENTS
08 71 00 DOOR HARDWARE
08 81 00 GLAZING
DIVISION 09 - FINISHES
09 65 00 RESILIENT FLOORING
09 90 00 PAINTS AND COATINGS
DIVISION 12 – FURNISHINGS
10 82 13 ROOF SCREENS
12 48 13 ENTRANCE FLOOR MATS AND FRAMES
DIVISION 21 – FIRE SUPPRESSION
PROJECT TABLE OF CONTENTS Page 2
DIVISION 22 – PLUMBING
22 14 23 STORM DRAINAGE PIPING SPECIALTIES
DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING (HVAC)
23 05 93 TESTING, ADJUSTING, AND BALANCING FOR HVAC
23 07 00 THERMAL INSULATION FOR MECHANICAL SYSTEMS
23 31 13.00 40 METAL DUCTS
23 34 23.00 40 HVAC POWER VENTILATORS
23 74 33.00 40 PACKAGED, OUTDOOR, HEATING AND COOLING MAKEUP AIR-
CONDITIONERS
DIVISION 26 - ELECTRICAL
26 05 19.00 10 INSULATED WIRE AND CABLE
26 20 00 INTERIOR DISTRIBUTION SYSTEM
26 51 00 INTERIOR LIGHTING
DIVISION 27 – COMMUNICATIONS
27 51 23.10 INTERCOMMUNICATION SYSTEM
DIVISION 28 - ELECTRONIC SAFETY AND SECURITY
28 20 01.00 10 ELECTRONIC SECURITY SYSTEM
28 23 23.00 10 CLOSED CIRCUIT TELEVISION SYSTEMS
28 31 00.00 10 FIRE DETECTION AND ALARM SYSTEM, DIRECT CURRENT LOOP
-- End of Project Table of Contents --
SECTION 00 01 15 Page 1
DOCUMENT 00 01 15
LIST OF DRAWINGS
02/11
PART 1 GENERAL
1.1 SUMMARY
This section lists the drawings for the project pursuant to contract clause
"DFARS 252.236-7001, Contract Drawings, Maps and Specifications."
1.2 CONTRACT DRAWINGS
Contract drawings are as follows:
DRAWING NO. REVISION NO. NAVFAC DWG
NO.
TITLE
T-001 TITLE SHEET
G-001 GENERAL NOTES & SYMBOLS
S-101 GENERAL NOTES, FRAMING PLANS, AND SECTIONS
A-001 ARCHITECTURAL SITE PLAN
AD-101 FIRST FLOOR DEMOLITION PLAN
AD-102 ROOF DEMOLITION PLAN
AD-201 DEMOLITION ELEVATIONS
AD-501 DEMOLITION DETAILS
AD-901 BID OPTION 1 – FIRST FLOOR DEMOLITION PLAN
AD-902 BID OPTION 1 – DEMOLITION ELEVATIONS
A-101 FIRST FLOOR CONSTRUCTION PLAN
A-102 ROOF CONSTRUCTION PLAN
A-111 FIRST FLOOR REFLECTED CEILING PLAN
A-121 FIRST FLOOR FURNITURE PLAN
A-201 BUILDING ELEVATIONS
A-301 BUILDING SECTIONS
A-501 MISCELLANEOUS DETAILS
A-502 ROOFING DETAILS
A-503 ROOFING DETAILS
A-504 DISPLAY SCREEN REMOVAL AND REINSTALLATION
DETAILS
A-601 DOOR & GLAZING SCHEDULE
A-901 BID OPTION 1 – FIRST FLOOR PLAN
A-902 BID OPTION 1 - ELEVATIONS
A-903 BID OPTION 1 - DETAILS
M-001 LEGEND
MD-101 FIRST FLOOR DEMOLITION PLAN
M-101 NEW WORK PLANS
M-601 SCHEDULES AND DETAILS
E-001 ELECTRICAL LEGEND
ED-101 FIRST FLOOR LIGHTING DEMOLITION PLAN
ED-201 FIRST FLOOR POWER DEMOLITION PLAN
ED-202 ROOF POWER DEMOLITION POWER PLAN
SECTION 00 01 15 Page 2
DRAWING NO. REVISION NO. NAVFAC DWG
NO.
TITLE
ED-301 FIRST FLOOR LOW VOLTAGE SYSTEMS DEMOLITION
PLAN
ED-302 ROOF LOW VOLTAGE SYSTEMS DEMOLITION PLAN
E-101 FIRST FLOOR LIGHTING PLAN
E-201 FIRST FLOOR POWER PLAN
E-202 ROOF POWER PLAN
E-301 FIRST FLOOR LOW VOLTAGE SYSTEMS PLAN
E-302 EXTERIOR LOW VOLTAGE SYSTEMS PLAN
E-401 ELECTRICAL RISER DIAGRAMS
E-501 ELECTRICAL PANEL SCHEDULES
E-601 ELECTRICAL DETAILS-1
E-602 ELECTRICAL DETAILS-2
E-603 ELECTRICAL DETAILS-3
E-604 ELECTRICAL DETAILS-4
P-101 ROOF PLUMBING PLAN
FA-001 FIRE ALARM GENERAL NOTES AND SYMBOLS
FA-D101 FIRE ALARM DEMO PLAN
FA-101 FIRE ALARM LAYOUT
1.3 SUPPLEMENTARY DRAWINGS
N/A
1.3.1 Reference Drawings
1.3.2 Boring Logs
1.3.3 Subsurface Data
-- End of Document --
SECTION 01 11 00 Page 1
SECTION 01 11 00
SUMMARY OF WORK
08/15
1.1 SUBMITTALS
Government approval is required for submittals with a "G" designation;
submittals not having a "G" designation are for Contractor Quality Control approval. 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:
1.2 WORK COVERED BY CONTRACT DOCUMENTS
1.2.1 Project Description
The work includes the renovation and upgrade of various components of the existing building including replacing the building electrical and fire alarm systems, roof including roof drains, AHU, bulletproof glazing panels on
East, North and West facades, entry door and framing, rubber flooring and plywood subflooring, repainting the ceiling, providing structural analysis, replacing CCTV system, installing new exterior security cameras, interior lock actuators and LED TVs, exterior cipher locks, installing new electrical panels, replacing rooftop bird deterrent system and snow melt system, and incidental related work.
1.2.2 Location
The work is located at the Times Square Recruiting Station on 7th Ave between 43rd and 44th Streets, New York, NY, approximately as indicated on contract plans or as directed by Contracting Officer or his representatives.
1.3 OCCUPANCY OF PREMISES
Building(s) will be unoccupied during performance of work under this
Contract.
The project site and the existing facility will physically be turned over to the Contractor for site fencing and demolition on or about 04 January 2017.
Prior to this project commencing an existing & continuing project for the city of New York will need to be completed by others.
Before work is started, arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.
1.4 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.
file://///GA-2K8/Proj/Proj/2015/201530_USACE%20Times%20Sq%20Recruiting%20Station/2%20Design/G%20Specs/01%2033%2000.DOC
SECTION 01 11 00 Page 2
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, existing work must be in a condition equal to or better than that which existed before new work started.
c. The Contractor shall protect the new paving recently installed around the area of Times Square Recruiting Station, Any damage to the new paving will be the Contractor's responsibility to repair to the initial condition.
1.5 LOCATION OF UNDERGROUND UTILITIES
Obtain digging permits prior to start of excavation, and comply with
Installation requirements for locating and marking underground utilities.
Contact local utility locating service a minimum of 48 hours prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work.
Identify and mark all other utilities not managed and located by the local utility companies. Scan the construction site with Ground Penetrating Radar
(GPR), electromagnetic, or sonic equipment, and mark the surface of the ground, pier deck or paved surface where existing underground utilities are discovered. Verify the elevations of existing piping, utilities, and any type of underground or encased obstruction not indicated, or specified to be removed, that is indicated or discovered during scanning, in locations to be traversed by piping, ducts, and other work to be conducted or installed.
Verify elevations before installing new work closer than nearest manhole or other structure at which an adjustment in grade can be made.
1.5.1 Notification Prior to Excavation
Notify the Contracting Officer at least 48 hours prior to starting excavation work.
1.6 GOVERNMENT-FURNISHED MATERIAL AND EQUIPMENT
1.7 GOVERNMENT-INSTALLED WORK
1.8 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
10 miles of the construction site.
Provide a salvage plan, listing material and equipment to be salvaged, and their storage location. Maintain property control records for material or equipment designated as salvage. Use a system of property control that is approved by the Contracting Officer. Store and protect salvaged materials and equipment until disposition by the Contracting Officer.
SECTION 01 11 00 Page 3
1.9 PERMITS
It shall be the Contractor's responsibility to secure all necessary city construction permits, as applicable.
PART 2 PRODUCTS
Not used.
PART 3 EXECUTION
Not used.
-- End of Section --
SECTION 01 14 00 Page 1
SECTION 01 14 00
WORK RESTRICTIONS
11/11
1.1 SUBMITTALS
approval. When used, a designation following the "G" designation identifies
SD-01 Preconstruction Submittals
Contractor regulations; G
Transportation of personnel, materials, and equipment; G
Purchase orders; G
List of Contact Personnel; G
Personnel List; G
Statement of Acknowledgement Form SF 1413; G
1.2 SPECIAL SCHEDULING REQUIREMENTS
a. Have materials, equipment, and personnel required to perform the work at the site prior to the commencement of the work.
b. Permission to interrupt any utility service must be requested in writing a minimum of 30 calendar days prior to the desired date of interruption. For disruption of the traffic pattern, the Contractor must give the City (DOT) a minimum of 14 calendar days notice prior to the disruption. The contractor shall coordinate all activities affecting the traffic pattern (both pedestrian and vehicular) with the
City DOT.
c. Any materials brought to the site by crane must be coordinated with the
City DOT. Additionally, this shall be done during the hours from midnight through 6:00AM. This may pertain to the new glass panels to be installed.
d. There will be a half marathon occurring in the beginning of March 2017.
The Contractor shall plan for a brief two-work day disruption.
e. From mid-December 2016 through 03 January 2017, the Times Square
Recruiting Booth is boarded up by the City in anticipation of the New
Year's Eve festivities.
file://///GA-2K8/Proj/Proj/2015/201530_USACE%20Times%20Sq%20Recruiting%20Station/2%20Design/G%20Specs/01%2033%2000.DOC
SECTION 01 14 00 Page 2
f. The Police Department will be responsible to remove their camera's that are currently on the facility. There is one on the roof also. The contractor shall coordinate with the Police Department as to when those cameras are taken down.
g. The contractor shall check and verify with the official Times Square public website (http://timessquarenyc.org/events/times-square-calendar/index.aspx) for upcoming events and activities that may affect construction in the area.
1.3 CONTRACTOR ACCESS AND USE OF PREMISES
1.3.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.
The Contractor shall not post any advertising signs on the construction fencing nor shall he allow third parties to do so either.
1.3.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.3.1.2 Identification Badges and Installation Access
1.3.1.3 No Smoking Policy
Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. 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.3.2 Working Hours
Regular working hours must consist of an 8 1/2 hour period established by the Contractor Officer, between 7 a.m. and 3:30 p.m., Monday through Friday, and 7 a.m. to 11 p.m. on Saturday, excluding Government holidays.
1.3.3 Work Outside Regular Hours
Work outside regular working hours requires Contracting Officer approval.
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.
SECTION 01 14 00 Page 3
1.3.4 Exclusionary Period
1.3.5 Occupied Buildings
1.3.6 Utility Cutovers and Interruptions
1.3.7 SHIPYARD AREA WORK CLEARANCE REQUEST
1.4 SECURITY REQUIREMENTS
Not Used
SECTION 01 32 01.00 10 Page 1
SECTION 01 32 01.00 10
PROJECT SCHEDULE
02/15
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 29R-03 (2011) Forensic Schedule Analysis
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; 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; Contracting Officer’s Representative to conduct review.
Project Scheduler Qualifications; G
Preliminary CPM Project Schedule; G
Initial CPM Project Schedule; G
Periodic CPM Schedule Updates; G
1.3 PROJECT SCHEDULER QUALIFICATIONS
Designate an authorized representative to be responsible for the preparation of the CPM 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.
file://///GA-2K8/Proj/Proj/2015/201530_USACE%20Times%20Sq%20Recruiting%20Station/2%20Design/G%20Specs/01%2033%2000.DOC
SECTION 01 32 01.00 10 Page 2
2.1 SOFTWARE
The scheduling software utilized to produce and update the schedules required herein must be capable of meeting all requirements of this specification.
2.1.1 Government Default Software
The Government intends to use Primavera P6.
2.1.2 Contractor Software
Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.
2.1.2.1 Primavera
If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.
2.1.2.2 Other Than Primavera
If the contractor chooses software other than Primavera P6, that is compliant with this specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at project completion.
3.1 GENERAL REQUIREMENTS
Prepare for approval a Project Schedule. 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 is the responsibility of the Contractor.
Contractor management personnel must actively participate in its development. 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
SECTION 01 32 01.00 10 Page 3
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:
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.
SECTION 01 32 01.00 10 Page 4
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. Submission of TAB specialist design review report.
i. Submission and approval of fire protection specialist.
j. N/A
k. Air balancing.
l. N/A
m. Controls testing plan submission.
n. Controls testing.
o. Performance Verification testing.
p. Other systems testing, if required.
q. Contractor's pre-final inspection.
r. Correction of punch list from Contractor's pre-final inspection.
s. Government's pre-final inspection.
t. Correction of punch list from Government's pre-final inspection.
u. 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: inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.
3.3.6 Standard Activity Coding Dictionary
Use the activity coding structure defined in the Standard Data Exchange
Format (SDEF) in ER 1-1-11. This exact structure is mandatory. 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 http://rms.usace.army.mil/
SECTION 01 32 01.00 10 Page 5
Field Activity Code Length Description
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, Government Furnished Property/Equipment (GFP) and Notice to Proceed
(NTP) for phasing requirements.
b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record);
ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE).
3.3.6.3 Area of Work Coding (AREA)
Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew from working in more than one work area at a time due to restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a
SECTION 01 32 01.00 10 Page 6 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
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 procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of
Work Code.
3.3.6.8 Feature of Work Coding (FOW)
Assign a Feature of Work Code to appropriate activities based on the
Definable Feature of Work to which the activity belongs based on the approved QC plan.
Definable Feature of Work is defined in Section 01 45 00.00 10 QUALITY
CONTROL. An activity can have only one Feature of Work Code.
3.3.7 Contract Milestones and Constraints
Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.
SECTION 01 32 01.00 10 Page 7
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.
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.
SECTION 01 32 01.00 10 Page 8
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.
a. Leads (negative lags) are prohibited.
b. Start to Finish (SF) relationships are prohibited.
3.3.15 Retained Logic
SECTION 01 32 01.00 10 Page 9
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.
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.
SECTION 01 32 01.00 10 Page 10
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.
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
SECTION 01 32 01.00 10 Page 11 meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS.
These updates will enable the Government to assess Contractor's progress.
a. Update information including Actual Start Dates (AS), Actual Finish
Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.
b. AS and AF dates must match the date(s) reported on the Contractor's
Quality Control Report for an activity start or finish.
3.5 SUBMISSION REQUIREMENTS
Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:
3.5.1 Data CD/DVDs
Provide two sets of data CD/DVDs containing the current project schedule and all previously submitted schedules in the format of the scheduling software
(e.g. .xer). Also include on the data CD/DVDs the Narrative Report and all required Schedule Reports. Label each CD/DVD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule must have a unique file name and use project specific settings.
3.5.2 Narrative Report
Provide a Narrative Report with each schedule submission. The Narrative
Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for any problems, either current or potential, which are revealed through that analysis. Include the following information as minimum in the Narrative Report:
a. Identify and discuss the work scheduled to start in the next update period.
b. A description of activities along the two most critical paths where the total float is less than or equal to 20 work days.
c. A description of current and anticipated problem areas or delaying factors and their impact and an explanation of corrective actions taken or required to be taken.
d. Identify and explain why activities based on their calculated late dates should have either started or finished during the update period but did not.
e. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, lag changes, resource changes, and actual start and finish date changes.
f. Identify and discuss out-of-sequence work.
3.5.3 Schedule Reports
SECTION 01 32 01.00 10 Page 12
The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer. Typically, reports contain
Activity Numbers, Activity Description, Original Duration, Remaining
Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish
Date, Total Float, Actual Start Date, Actual Finish Date, and Percent
Complete. Provide the reports electronically in .pdf format. Provide 2 sets of hardcopy reports. The following lists typical reports that will be requested:
3.5.3.1 Activity Report
List of all activities sorted according to activity number.
3.5.3.2 Logic Report
List of detailed predecessor and successor activities for every activity in ascending order by activity number.
3.5.3.3 Total Float Report
A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.
3.5.3.4 Earnings Report by CLIN
A compilation of the Total Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original
Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).
3.5.3.5 Schedule Log
Provide a Scheduling/Leveling Report generated from the current project schedule being submitted.
3.5.4 Network Diagram
The Network Diagram is required for the Preliminary, Initial and Periodic
Updates. 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.4.1 Continuous Flow
Show a continuous flow from left to right with no arrows from right to left.
Show the activity number, description, duration, and estimated earned value on the diagram.
SECTION 01 32 01.00 10 Page 13
3.5.4.2 Project Milestone Dates
Show dates on the diagram for start of project, any contract required interim completion dates, and contract completion dates.
3.5.4.3 Critical Path
Show all activities on the critical path. The critical path is defined as the longest path.
3.5.4.4 Banding
Organize activities using the WBS or as otherwise directed to assist in the understanding of the activity sequence. Typically, this flow will group activities by major elements of work, category of work, work area and/or responsibility.
3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram
With each schedule submission, provide a SVC diagram showing 1) Cash Flow S-
Curves indicating planned project cost based on projected early and late activity finish dates, and 2) Earned Value to-date.
3.6 PERIODIC SCHEDULE UPDATE
3.6.1 Periodic Schedule Update Meetings
Conduct periodic schedule update meetings for the purpose of reviewing the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and progress payment. Conduct meetings at least monthly within five days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows all meeting participants to view the proposed schedule during the meeting. The Contractor's authorized scheduler must organize, group, sort, filter, perform schedule revisions as needed and review functions as requested by the Contractor and/or
Government. The meeting is a working interactive exchange which allows the
Government and Contractor the opportunity to review the updated schedule on a real time and interactive basis. The meeting will last no longer than 8 hours. Provide a draft of the proposed narrative report and schedule data file to the Government a minimum of two workdays in advance of the meeting.
The Contractor's Project Manager and scheduler must attend the meeting with the authorized representative of the Contracting Officer. Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work. Following the periodic schedule update meeting, make corrections to the draft submission. Include only those changes approved by the Government in the submission and invoice for payment.
3.6.2 Update Submission Following Progress Meeting
Submit the complete Periodic Schedule Update of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 work days after the periodic schedule update meeting.
3.7 WEEKLY PROGRESS MEETINGS
SECTION 01 32 01.00 10 Page 14
Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled PERIODIC
SCHEDULE UPDATE MEETINGS for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks. Use the current approved schedule update for the purposes of this meeting and for the production and review of reports. At the weekly progress meeting, address the status of
RFIs, RFPs and Submittals.
3.8 REQUESTS FOR TIME EXTENSIONS
Provide a justification of delay to the Contracting Officer in accordance with the contract provisions and clauses for approval within 10 days of a delay occurring. Also prepare a time impact analysis for each Government request for proposal (RFP) to justify time extensions.
3.8.1 Justification of Delay
Provide a description of the event(s) that caused the delay and/or impact to the work. As part of the description, identify all schedule activities impacted. Show that the event that caused the delay/impact was the responsibility of the Government. Provide a time impact analysis that demonstrates the effects of the delay or impact on the project completion date or interim completion date(s). Evaluate multiple impacts chronologically; each with its own justification of delay. With multiple impacts consider any concurrency of delay. A time extension and the schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.
3.8.2 Time Impact Analysis (Prospective Analysis)
Prepare a time impact analysis for approval by the Contracting Officer based on industry standard AACE 52R-06. Utilize a copy of the last approved schedule prior to the first day of the impact or delay for the time impact analysis. If Contracting Officer determines the time frame between the last approved schedule and the first day of impact is too great, prepare an interim updated schedule to perform the time impact analysis. Unless approved by the Contracting Officer, no other changes may be incorporated into the schedule being used to justify the time impact.
3.8.3 Forensic Schedule Analysis (Retrospective Analysis)
Prepare an analysis for approval by the Contracting Officer based on industry standard AACE 29R-03.
3.8.4 Fragmentary Network (Fragnet)
Prepare a proposed fragnet for time impact analysis consisting of a sequence of new activities that are proposed to be added to the project schedule to demonstrate the influence of the delay or impact to the project's contractual dates. Clearly show how the proposed fragnet is to be tied into the project schedule including all predecessors and successors to the fragnet activities. The proposed fragnet must be approved by the
Contracting Officer prior to incorporation into the project schedule.
3.8.5 Time Extension
SECTION 01 32 01.00 10 Page 15
The Contracting Officer must approve the Justification of Delay including the time impact analysis before a time extension will be granted. No time extension will be granted unless the delay consumes all available Project
Float and extends the projected finish date ("End Project" milestone) beyond the Contract Completion Date. The time extension will be in calendar days.
Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay will not be a cause for an extension to the performance period, completion date, or any interim milestone date.
3.8.6 Impact to Early Completion Schedule
No extended overhead will be paid for delay prior to the original Contract
Completion Date for an Early Completion IPS unless the Contractor actually performed work in accordance with that Early Completion Schedule. The
Contractor must show that an early completion was achievable had it not been for the impact.
3.9 FAILURE TO ACHIEVE PROGRESS
Should the progress fall behind the approved project schedule for reasons other than those that are excusable within the terms of the contract, the
Contracting Officer may require provision of a written recovery plan for approval. The plan must detail how progress will be made-up to include which activities will be accelerated by adding additional crews, longer work hours, extra work days, etc.
3.9.1 Artificially Improving Progress
Artificially improving progress by means such as, but not limited to, revising the schedule logic, modifying or adding constraints, shortening activity durations, or changing calendars in the project schedule is prohibited. Indicate assumptions made and the basis for any logic, constraint, duration and calendar changes used in the creation of the recovery plan. Any additional resources, manpower, or daily and weekly work hour changes proposed in the recovery plan must be evident at the work site and documented in the daily report along with the Schedule Narrative Report.
3.9.2 Failure to Perform
Failure to perform work and maintain progress in accordance with the supplemental recovery plan may result in an interim and final unsatisfactory performance rating and/or may result in corrective action directed by the
Contracting Officer pursuant to FAR 52.236-15 Schedules for Construction
Contracts, FAR 52.249-10 Default (Fixed-Price Construction), and other contract provisions.
3.9.3 Recovery Schedule
Should the Contracting Officer find it necessary, submit a recovery schedule pursuant to FAR 52.236-15 Schedules for Construction Contracts.
3.10 OWNERSHIP OF FLOAT
Except for the provision given in the paragraph IMPACT TO EARLY COMPLETION
SCHEDULE, float available in the schedule, at any time, may not be
SECTION 01 32 01.00 10 Page 16 considered for the exclusive use of either the Government or the Contractor including activity and/or project float. Activity float is the number of work days that an activity can be delayed without causing a delay to the
"End Project" finish milestone. Project float (if applicable) is the number of work days between the projected early finish and the contract completion date milestone.
3.11 TRANSFER OF SCHEDULE DATA…
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 .