Exhibit B 01 32 13 Scheduling of Work.pdf

FBOP TECHNICAL DESIGN GUIDELINES Construction & Environmental Review

FOR NEW INSTITUTION CONSTRUCTION SECTION REVISION DATE: 03-01-21

SCHEDULING OF WORK 01 32 13-1

Sensitive But Unclassified – SBU

SECTION 01 32 13 - SCHEDULING OF WORK

PART 1 - GENERAL

1.1 SUMMARY

A. Section Includes:

1. Critical Path Method Schedule requirements.

2. Contractor’s scheduling representative.

3. Contract schedule (logic) submission and review process.

4. Contract schedule (cost and resource loading) submission and review process.

5. Project schedule updating.

6. Change modifications.

7. Responsibility for completion.

8. Performance monitoring.

9. Scheduling software requirements.

B. Related Sections and Documents:

1. The Project Schedule shall be in accordance with this Section and the FAR Clause, 52.236-15, Schedules for Construction Contracts.

2. Project Meetings are described in 01 31 19 - PROJECT

MEETINGS.

3. Drawings and general provisions of Contract and other Division 01 Requirements apply to this Section.

4. Proposed Contract Performance Schedule in Section J of the Phase Two Solicitation.

1.2 RELATED SECTIONS AND DOCUMENTS

A. Provide a detailed project schedule with activity entries for each portion of the design and construction work, in chronological order, cumulatively indicating the entire Contract Performance Period. The detailed project

SCHEDULING OF WORK 01 32 13-2

schedule shall incorporate and be developed from the Contractor’s Proposed Design Build Schedule, submitted with the Phase Two Proposal. The Detailed Schedule shall employ the Critical Path Method (CPM) using retained logic for the planning, scheduling, and reporting of the work to be performed under the contract. The schedule will be produced utilizing the most current version of the Primavera Project Planner Software System, or fully transferable to Primavera Project Planner (refer to SCHEDULING SOFTWARE). The type of schedule shall be a Precedence Diagramming Method (PDM). Definitions applicable to this Section include the following:

1. Project Schedule - The Project Schedule includes the Detailed Project Baseline Schedule, subsequent Project Schedule updates and revisions and computer produced reports as stipulated in the requirements.

2. Critical Path - The Critical Path is the sequence of activities in the Project Schedule network which requires the longest total amount of time to complete the Work.

3. Network - The Network is the graphic representation of the Project Schedule prepared using the Critical Path Method. The network shows the sequence and interdependence of the activities, and planned and actual progress by activity, required for complete performance of the work.

4. Working Day - A Working Day is a calendar day scheduled for active performance of Contract requirements.

5. Key Plans - The Key Plans are graphic representations of the Contractor’s planned breakdown of the project for scheduling purposes. The key plans will clearly define the boundaries of the work for each designated area. The alpha-numeric codes on the key plans shall match the code values for the "Area" in the schedule as described herein. See 7.a.11.d for the minimum Work Area breakdown to be depicted on the Key Plans.

6. Time Impact Analysis - The Time Impact Analysis shall demonstrate the comparison of the time impact for each schedule revision or proposed revision against the currently accepted Project Schedule.

B. The entire contract performance period as established by the Contract shall establish a Final Contract Completion Date and shall be utilized in the planning and presentation of the Contractor’s Project Schedule. As the Detailed Schedule is being developed, the Contractor may project an earlier completion date. The government may elect to accept a schedule

SCHEDULING OF WORK 01 32 13-3

that projects an earlier completion date; however, this acceptance shall not modify the Final Contract Completion Date. The time difference between the Contractor’s projected completion date and the Final Contract Completion Date shall be owned and for the mutual use of both the Contractor and the Government. The Government reserves the right not to accept any schedule it determines to be unrealistic in length.

C. The purpose of the Project Schedule shall be to:

1. Assure adequate planning, staffing, scheduling, and reporting during execution of the work by the Contractor.

2. Assure coordination of the work among the design build team, subcontractors, consultants, and suppliers at tiers.

3. Assist the Contractor and Contracting Officer in monitoring the progress of the work and evaluating proposed changes to the Contract and the Project Schedule.

4. Assist the Contracting Officer and the Contractor in the preparation and evaluation of the Contractor’s monthly progress payments.

D. The Contractor shall provide the computer processing of the network computer produced schedule, graphics and cost reports required under the contract at no additional cost to the Government.

1.3 SUBMITTALS

A. Within seven (7) calendar days after the date of the initial Notice to Proceed, the Contractor shall designate in writing an authorized scheduling representative in the Contractor’s organization who shall be responsible for coordinating with the Contracting Officer during the preparation and maintenance of the Project Schedule. The Contractor’s scheduling representative may not be replaced by the Contractor without prior written consent by the Contracting Officer.

B. The Contractor’s scheduling representative shall have complete authority to act on behalf of the Contractor in fulfilling the Project Schedule requirements of the Contract and such authority shall not be interrupted throughout the duration of the Contract unless approved in writing by the Contracting Officer.

C. The Contractor agrees that whenever the Contracting Officer shall inform the Contractor in writing that the Contractor’s scheduling representative is not performing his duties to the satisfaction of the Government, the Contractor shall replace such representative at no additional cost to the Government and designate in writing, within seven (7) calendar days of

SCHEDULING OF WORK 01 32 13-4

notification from the Contracting Officer, a new authorized representative satisfactory to the Contracting Officer.

1. The Contractor’s scheduling representative, the Project Superintendent and the individual who is responsible for developing and inputting information into the schedule (if they are different individuals) shall attend schedule related meetings and monthly update meetings throughout the duration of the project.

D. Project Schedule Requirements/ Proposed Design Build Schedule Review Meeting - The Contractor shall meet with the Contracting Officer within fourteen (14) calendar days after the date of the Notice to Proceed to conduct a joint review of the Project Schedule requirements of the Contract to assure the Government of the Contractor’s and subcontractor's understanding of the requirements. A review of the Contractor’s Proposed Design Build Schedule shall also be made with the opportunity for minor logic revisions to be proposed by either the Contractor or the Government. The Contractor shall coordinate this meeting with the Initial Design Meeting described in the Design Procedures Section 01 00 05 of the FBOP Technical Design Guidelines.

1.4 REFERENCES AND/OR CODES

A. The Project Schedule (Logic) for Package A shall be submitted with the Preliminary Design Documents for Package A. The Project Schedule (Logic) for Package B shall be submitted with the Preliminary Design Documents for Package B. If an Early Sitework Package is submitted, the schedule logic, cost and manpower loading shall be submitted with the design documents for that package. The Contractor shall submit for the Contracting Officer’s review, computer discs and five (5) prints (Time-scaled Logic Diagram) of its proposed Project Schedule (Logic) hereafter referred to as the Project Schedule. The Project Schedule shall be neatly organized and plotted time scaled from left to right on either 24" X 35" or 30" X 42" standard size sheets with suitable notation relating the interface points among sheets. The Project Schedule shall consist of, but not be limited to, the following activities:

1. Design Document and Schedule development, submissions, government review periods, joint meetings, approval/acceptance for all proposed packages. FBOP’s review periods shall be clearly identifiable as separate activities.

2. Proposed long lead procurement activities.

3. Proposed sequencing of activities.

SCHEDULING OF WORK 01 32 13-5

4. Milestone events as required by the Contract, Contract Documents and Contract Clauses.

5. Proposed area (location) of activities.

6. Proposed phase of activities.

7. Proposed Consultant, Subcontractor and Trade breakdown.

Contractor’s self-performed work shall be clearly identifiable.

8. Proposed procurement phase activities.

9. The proposed procurement activities shall include mobilization, shop drawings and sample submittals and the fabrication and delivery of key and long-lead procurement elements. The Project Schedule shall indicate intended submittal dates.

10. Requested substitutions, shall be identified as network activities in the procurement phase activities. The minimum duration for FBOP review of these activities shall be 45 calendar days for requested substitutions.

11. Testing and Commissioning: Activities shall be provided for the testing and commissioning of the following:

a. Fire suppression, mechanical, electrical, and electronic systems, and equipment.

b. Food service, medical, laundry and elevator equipment.

12. Delivery dates for items furnished by the government and installed by the contractor.

13. Each activity in the Project Schedule shall contain the following:

a. The Contractor shall submit to the Contracting Officer for review and approval the prepared activity number structure.

b. Concise description of the work represented by the activity (maximum forty-eight (48) characters). The work related to each activity shall be limited to one work trade and one area.

Activity descriptions shall include area designations which match the key plans submitted by the Contractor.

c. Proposed activity durations shall be in units of whole working days. Design development activities shall be by phase (“Develop Preliminary Package B Documents”). All activities, with the exception of design and long lead

SCHEDULING OF WORK 01 32 13-6

procurement activities shall have a maximum duration of fifteen (15) working days.

d. Work area code for design and construction activities (maximum six (6) characters). Abbreviations shall be fully described in a legend attached to the Project Schedule. The Contractor shall provide, without additional cost to the Government Key Plans, graphic illustrations of the relationship of construction activities to intended work areas on prints of the Contract Drawings. The minimum requirement for Work Area Codes on a project shall be the following (if part of the project):

1) AO Administration/Entry Building

2) UP Central Utility Plant

3) FR Firing Range

4) GL Garage/Landscape

5) GT Guard Tower

6) OW Outside Warehouse

7) UW UNICOR Warehouse

8) SG Access for Vehicles and Support

9) AI Administration (inside)

10) EM Education/Multi-Use

11) FS Food Service

12) HS Health Services

13) MS Maintenance Shops

14) PS Personal Services

15) RE Recreational Services

16) UF UNICOR-Federal Prison industries

17) VT Vocational Services

SCHEDULING OF WORK 01 32 13-7

18) H1-H6 General Inmate Housing Units (broken down by building or floor for multi-story construction)

19) SH Special Housing Units

20) ST Staff Training Building

21) SW Sitework

Note: For high rise construction the minimum designation for Work Area Codes shall be each floor.

e. Performance responsibility by discipline code: MECH, ELEC, etc., or other acceptable abbreviations approved by the Contracting Officer (maximum of six (6) characters).

Each consultant and subcontractor shall be coded separately and each trade within each subcontract shall also be coded separately. Abbreviations shall be fully described in a legend attached to the Project Schedule.

f. The Contractor shall identify the area (location) in which the activity is to be performed.

g. The Contractor shall identify the phase of the project in which the activity is to be performed.

h. The Contractor shall be responsible for assuring that all consultant, subcontractor, and supplier work, as well as its own work, is included in the Project Schedule.

i. The Project Schedule shall show the sequence and interdependence of activities required for complete performance of the work. The Contractor shall be responsible for assuring work sequences are logical and the Project Schedule shows a coordinated plan of the work.

j. Proposed durations assigned to each activity shall be the Contractor’s best estimate of time required to complete the activity considering the scope and resources planned for the activity.

k. Failure by the Contractor to include an element of work required for performance of the Contract shall not excuse the Contractor from completing work within the Contract time. In the event the Contractor fails to define an element of work, activity or logic and the Contracting Officer’s review does not

SCHEDULING OF WORK 01 32 13-8

detect this omission or error, such omission or error, when discovered by the Contractor or Contracting Officer, shall be corrected by the Contractor, and accepted by the Contracting Officer in fragnet form prior to incorporation in the next Schedule Revision (discussed hereinafter). These corrections shall not affect the Contract time.

l. Normal, seasonal, and adverse weather conditions shall be considered and included in the planning and scheduling of work. Include the influence of high or low ambient temperatures and/or precipitation to ensure completion of work within the Contract time. Normal, seasonal, and adverse weather conditions shall be determined by an assessment of average historical climatic conditions based upon the preceding ten (10) year records published for the locality by the National Ocean and Atmospheric Administration (NOAA) and entitled, "Local Climatological Data." Refer to the Contract Clauses.

B. Within fourteen (14) calendar days of receipt of the Contractor’s Detailed Project Schedule (Logic) submission for Package A and twenty-one (21) calendar days of receipt of the Contractor’s Detailed Project Schedule (Logic) submission for Package B, the FBOP will deliver a completed Project Schedule (Logic) Review Report to the Contractor. Within seven

(7) calendar days of receipt of the Contractor’s Detailed Schedule Logic and cost and manpower loading for an Early Sitework Package (Optional), the FBOP will deliver a completed Schedule Review Report to the Contractor. The Contractor shall be prepared to address the FBOP’s comments at the Detailed Schedule Logic Review Meetings for each package.

C. Project Schedule Logic Review Meetings for Package A and B - The Contracting Officer and the Contractor shall meet within twenty-one (21) calendar days of receipt of the Contractor’s Project Schedule (Logic) submission for Package A and twenty-eight (28) calendar days of receipt of the Contractor’s Project Schedule (Logic) submission for Package B for joint review, correction, or adjustment of the proposed Network. All submissions after the initial Project Schedule for Package A shall be an update of the original Project Schedule and include all the activities from the previous submission.

1. The FBOP may reject the Contractor’s Project Schedule (Logic). If rejected, the contractor shall, within seven (7) calendar days revise the Project Schedule and submit computer discs and five (5) prints (Time-scaled Logic Diagram) of the revised Project Schedule. The revision shall incorporate comments noted in the FBOP’s written reports and comments and agreements made during the Project

SCHEDULING OF WORK 01 32 13-9

Schedule Review Meeting. The Contracting Officer shall have seven (7) calendar days after receipt of the revised Project Schedule for review and either acceptance or issuance of additional comments.

1.5 SYSTEM DESCRIPTION:

A. The Project Schedule (Logic), which has been updated with Cost and Resource Loading for Package A activities shall be submitted with the Final Design Documents for Package A. The updated Project Schedule with Cost and Resource Loading for Package B activities shall be submitted with the Final Design Documents for Package B. The format requirements for these submissions shall be the same as for the logic submissions.

B. The following shall be depicted for each activity:

1. The assigned dollar value (cost-loading) shall cumulatively equal the Contract price. In order to invoice directly for mobilization, bond and insurance costs, these items shall be shown as separate activities. General requirement costs, overhead and profit, etc., shall be prorated throughout the activities of the Schedule. Delivery activities may not be cost-loaded and shown separate from the related fabrication activity. Activity costs shall be stated in at least the same level of detail as and shall correlate with the total contract price.

2. The cost-loading of final testing and commissioning activities shall be a minimum of 5% of the total cost of the related systems and/or equipment. At a minimum this is to include elevator, food service, plumbing, mechanical, electrical, and electronic systems and equipment.

a. The cost-loading for punch list and incomplete items identified in Sections 01 70 00 - PROJECT CLOSEOUT and

28 50 00 - SECURITY ELECTRONICS GENERAL

PROVISIONS, shall be a minimum of 2% of the total Contract price. These closeout requirements shall include but are not limited to completion of the punch lists issued by the Government at Substantial Completion; submission of all remaining contract deliverables including close out submittals, spare parts, and Record Documents; completion of final cleanup of the premises; and vacating the site.

b. The manpower-loading shall indicate the total number of workers, not total number of crews.

SCHEDULING OF WORK 01 32 13-10

3. The Contractor shall prepare and submit a (separate) cumulative cost loading graphic chart based on early and late start dates. The graph shall show the cumulative cost over the duration of the Project Schedule. This cumulative cost graph shall be computer generated from the Contractor’s schedule data. The Contractor shall also prepare and submit a (separate) manpower per day summary analysis in graphic format, depicting man-days by principal trades and aggregate. The graph shall show the number of man-days of effort, by month, over the duration of the Project Schedule. This man loading graph shall be computer generated from the Contractor’s schedule data.

4. Within twenty-one (21) calendar days of receipt of the Contractor’s Project Schedule (Loading) submission for Package A and twenty-one (21) calendar days of receipt of the Contractor’s Project Schedule (Loading) submission for Package B, the FBOP will deliver a completed Project Schedule (Loading) Review Report to the Contractor. This report shall be written in narrative format, using separate comments to address each individual issue. The Contractor shall be prepared to address the FBOP’s comments at the Project Schedule Loading Review Meetings for each package.

C. Project Schedule Loading Review Meetings for Package A and B - The Contracting Officer and the Contractor shall meet within twenty-eight (28) calendar days of receipt of the Contractor’s Package A Loading and twenty-eight (28) calendar days of receipt of the Contractor’s Package B Loading submission for joint review, correction or adjustment of the proposed network and resource loading. Areas which, in the opinion of the Contracting Officer, conflict with timely completion of the Project shall be subject to revision by the Contractor.

1. In the event the Contractor fails to define an element of work, activity or logic and the Contracting Officer’s review does not detect this omission or error, such omission or error, when discovered by the Contractor or Contracting Officer, shall be corrected by the Contractor, and accepted by the Contracting Officer in fragnet form prior to incorporation in the next Schedule Revision (discussed hereinafter). This correction shall not affect the Contract time.

2. Within seven (7) calendar days after each joint review meeting between the Contractor and Contracting Officer, the Contractor shall revise the Project Schedule in accordance with agreements reached during the joint review and submit computer discs and five

(5) prints (Time-scaled Logic Diagram) of the revised Project Schedule. The Contracting Officer shall have seven (7) calendar days after receipt of the revised Project Schedule for review and either acceptance or issuance of additional comments.

SCHEDULING OF WORK 01 32 13-11

3. Upon establishment of an agreed-upon Project Schedule, the Contractor’s Scheduling Representative, and Project Superintendent shall sign and date on the face of the Project Schedule documents (the Network and computer produced Schedule and Cost Report), which shall then indicate the Contractor’s acceptance and approval of the Project Schedule.

Final review and acceptance by the Contracting Officer will take place at the review meeting. The Contracting Officer shall sign and date on the face of the Project Schedule documents, which shall then indicate the acceptance of the Project Schedule.

4. Upon acceptance of the Project Schedule by the Contracting Officer, the cost-loaded values of the Project Schedule and progress of activities will be used as a basis for determining progress payments. Monthly progress payments shall be based upon information developed by the monthly schedule update. The computer-produced Cost Report will be utilized by the Contracting Officer for verification of the Application for Payment submitted by the Contractor. Acceptance by the Contracting Officer of the Contractor’s Project Schedule does not relieve the Contractor of responsibility whatsoever for the accuracy or feasibility of the Project Schedule, or of the Contractor’s ability to meet the Contract Completion Date. Such acceptance does not create a warranty, expressed or implied, or acknowledge or admit the reasonableness of the activities, logic, durations, manpower, cost, or equipment loading of the Contractor’s Project Schedule.

1.6 DEFINITIONS

A. The Project Schedule shall be updated on a monthly basis throughout the entire Contract time and until Project Completion. The Contractor shall meet with the Contracting Officer each month at a Schedule Update Meeting to review actual progress made through the data date of the Schedule Update, including the dates activities were started and/or completed. The data date of each schedule update shall be on or before the seventh (7th) day preceding the progress payment submittal deadline.

The Contractor shall submit one (1) original and three (3) reproduced marked-up copies of the currently accepted Project Schedule and computer produced reports coordinated with the requirements above.

This submission shall contain the following information:

1. Actual activity start and/or complete dates, revised (current) remaining durations, and percent complete with regard to activity cost/progress.

SCHEDULING OF WORK 01 32 13-12

2. The Contractor shall indicate in writing current or anticipated conditions which may delay the work.

a. Any additional written information necessary to support the above.

3. In case of disagreements at the schedule update meeting concerning actual progress to date the Contracting Officer's determination shall govern.

4. Upon completion of the Schedule Update Meeting, which shall occur on or before the seventh (7th) day preceding the progress payment submittal deadline, the Contractor shall update the Project Schedule to reflect progress as of the data date of the Schedule Update and carry out a computer produced calculation to determine the status of the Project Schedule. The Contractor shall process the schedule within three (3) calendar days and forward the update and pay request to the Contracting Officer. The Contracting Officer shall review the update upon receipt and shall process the monthly request for payment based upon the accepted update.

5. Each Project Schedule Update, based upon the Contractor’s input as discussed above, will be forwarded to the Contracting Officer, and will include:

a. A list of activities completed during the preceding month.

b. A list of activities started but not completed during the preceding month, including percent complete.

c. Computer discs (2 copies).

d. The following computer produced reports (unless modified by the Contracting Officer):

1) Total Float Report by Area.

2) Detailed Cost Report by Subcontractor.

3) Summary Cost Report by Subcontractor.

4) 60-Day Look-Ahead Bar Chart by Area (Early and Late Bars).

5) Summary Bar Chart by Area.

6) Detailed Bar Chart by Area (Early and Late Bars).

SCHEDULING OF WORK 01 32 13-13

7) Early Start Sort of Activities by Area.

e. The Total Float and Early Start computer produced Schedule Reports list above shall include, for each activity depicted on the Network, the following information:

1) Activity Number(s).

2) Activity Description.

3) Original Duration.

4) Remaining Duration.

5) Activity Responsibility Code.

6) Activity Early Start Date.

7) Activity Early Finish Date.

8) Activity Late Start Date.

9) Activity Late Finish Date.

10) Total Float.

11) Percent Complete.

12) Actual Start Date.

13) Actual Finish Date.

f. If the Contracting Officer does not record exceptions to the submitted Project Schedule Update within seven (7) calendar days of its receipt, the Contracting Officer will be deemed to have accepted it.

g. The monthly updating of the Project Schedule shall be an integral part and basic element of the estimate upon which progress payments will be made. If, in the judgment of the Contracting Officer, the Contractor fails or refuses to provide information required to accomplish a complete Project Schedule Update or revision as specified hereafter, the Contractor shall be deemed to have not provided the required estimate upon which progress payments may be made and shall not be entitled to progress payments until it has furnished the information necessary for a complete

SCHEDULING OF WORK 01 32 13-14

Schedule Update to the satisfaction of the Contracting Officer.

B. Project Schedule Revisions:

1. Updating the Project Schedule to reflect actual progress made up through the data date of a Schedule Update shall not be considered revisions to the Project Schedule.

2. If it appears the Project Schedule no longer represents the actual prosecution and the progress of the work, the Contracting Officer will request, and the Contractor shall submit, a revision to the Project Schedule.

3. The Contractor may request revisions to the Project Schedule in the event the Contractor’s planning for the work is revised. If the Contractor desires to make changes in the Project Schedule to reflect revisions in its’ method of operating and scheduling of the work, the Contractor shall submit proposed revisions in fragnet (subnet) form and state in writing the reason for the proposed revision and anticipated effect of the revision on the Project Schedule and Project Completion. See paragraph on Fragnet Meetings below for minimum requirements when submitting a fragnet. Accepted revisions will be incorporated into a revised Project Schedule which will become the current accepted Project Schedule and used for future updates and revisions.

4. The Contracting Officer may also request revisions to the Project Schedule. Within seven (7) days from receipt of the Contracting Officer’s request the Contractor shall submit the proposed revision in fragnet (subnet) form along with a statement agreeing with the proposed change or setting forth justification why it should not be accomplished. The Contractor shall also submit detailed notification of any cost implications of the proposed change. See paragraph on Fragnet Meetings below for minimum requirements when submitting a fragnet. If accepted by both parties the revisions will be incorporated into a revised Project Schedule which will become the current accepted Project Schedule and used for future updates and revisions. If the Contractor’s justification for not accomplishing the revision is accepted, such revision will not be incorporated into the Project Schedule. The Contracting Officer reserves the right to direct the Contractor to incorporate the proposed revision. Cost implications of the revision, if any, shall be incorporated into the Project through a Contract Modification.

5. The Contractor shall attend weekly Fragnet Meetings to review change modifications, potential delays, delays, or requested

SCHEDULING OF WORK 01 32 13-15

revisions to the schedule. The Contractor’s representative(s) attending the meeting shall be authorized to make any and all decisions regarding prosecution of the work and schedule management. Either the Contractor or the Owner may bring proposed fragnets to be incorporated into a copy of the currently approved schedule. At a minimum, the fragnets shall list the reason for the fragnet, affected activities by activity ID and activity description, proposed logic, proposed duration, logic ties, order of incorporation if more than one fragnet is proposed, schedule in which the fragnet will be incorporated and the anticipated affect upon associated activity paths and Project Completion. In addition, the Contractor shall bring a Time-scaled Logic Diagram printed from the current accepted Project Schedule indicating activity ID, activity description, original duration, remaining duration, logic ties, total float, free float, and/or other information as requested by the Contracting Officer for each activity (for assistance in reviewing each proposed fragnet). Both parties shall sign and date the proposed fragnet indicating approval for incorporation into a copy of the current accepted Project Schedule for purposes of initial evaluation of the fragnet. Note: Fragnets can be proposed at any time either party feels necessary, not just at the Weekly Fragnet Meeting. The Contractor shall maintain the working copy of the current accepted Project Schedule incorporating the fragnets throughout the month.

6. Requests for revisions of activity manpower, activity costs, or redistribution of activity costs shall be made in accordance with the above requirements.

1.7 QUALITY ASSURANCE

A. When change modifications are proposed, potential delays are anticipated, delays are experienced, or the Contractor desires to revise the Project Schedule, the Contractor shall submit to the Contracting Officer a written Time Impact Analysis illustrating the influence of each modification, potential delay, delay, or Contractor request on the contract time. This analysis shall be developed and submitted at the earliest time the Contractor becomes aware of a delay or potential delay. The preparation of Time Impact Analyses is considered part of the construction process and will be performed at no additional cost to the Government.

Each Time Impact Analysis shall include a Fragmentary Network (Network analysis) demonstrating how the Contractor proposes to incorporate the modification, potential delay, delay, or Contractor request into the Project Schedule. The Time Impact Analysis shall demonstrate the time impact of the change modification or potential delay. Past impacts shall be analyzed based on the accepted schedule at the time of the impact and

SCHEDULING OF WORK 01 32 13-16

future impacts shall be analyzed based on the current accepted Project Schedule. The event times used in the Time Impact Analysis shall be those included in the accepted project schedule at the time of the impact or as adjusted by mutual agreement.

1. Activity delays shall not automatically mean that an extension of the Contract time is warranted or due the Contractor. It is possible that a modification or delay will not affect existing critical activities or cause non-critical activities to become critical. A modification or delay may result in only absorbing a part of the available total float that may exist within an activity chain of the Network, thereby not causing effect on the Contract time.

2. Float is not for the exclusive use or benefit of either the Government or the Contractor. An extension of the Contract time will be granted only to the extent the equitable time adjustments to the activity or activities affected by the modification or delay, exceeds the total float of an activity; and, after re-sequencing Work to the maximum possible at no increase in construction cost to the Government, forces the activity onto the critical path; and extends the contract time set forth in the Contract Clauses.

3. Four (4) copies of each Time Impact Analysis shall be submitted as follows:

a. Along with the proposal for requested change.

b. Within seven (7) calendar days after receipt of a written modification.

c. Within seven (7) calendar days after the furnishing of a written notice by the Contracting Officer.

d. Within seven (7) calendar days from the beginning of a delay from unforeseeable causes.

4. In cases where the Contractor does not submit a Time Impact Analysis within the time stated above, it is mutually agreed that the particular modification, delay, or Contractor request does not require an extension of the contract time.

5. Approval or rejection of each Time Impact Analysis by the Contracting Officer shall be made after receipt of each Time Impact Analysis unless subsequent meetings and negotiations are necessary. Upon approval, a copy of the Time Impact Analysis signed by the Contracting Officer shall be returned to the Contractor and incorporated into the Project Schedule at the next

SCHEDULING OF WORK 01 32 13-17

Schedule revision which will become the current accepted Project Schedule.

6. Time Impact Analyses that result in an extension of the Contract time and/or change modification work shall be incorporated into and attached to the applicable change modification(s).

1.8 WARRANTY

A. The Contractor shall furnish sufficient forces, offices, facilities, and equipment, and shall work such hours including night shift and overtime operations, as necessary to ensure the prosecution of the Work in accordance with the current monthly Project Schedule Update. If the Contractor falls behind in meeting the Project Schedule as noted by an extended contract completion date in the current monthly Project Schedule Update, the Contractor shall take such steps as may be necessary to improve its progress without additional cost to the Government. The provision of this paragraph shall not be construed as prohibiting the Contractor from increasing the hours of work, the number of shifts, overtime operations and/or the amount of construction plant and equipment or working on Saturdays, Sundays, and holidays, provided the Contractor gives reasonable notice to the Contracting Officer.

1. Failure of the Contractor to comply with the requirements of this paragraph shall be a basis for determination by the Contracting Officer that the Contractor is not prosecuting the work with such diligence as will ensure completion within the contract time. Upon such determination, the Contracting Officer may terminate the Contractor’s right to proceed with the work or separable part thereof, in accordance with the provisions of the Contract Clauses or may take such other actions as may be deemed appropriate.

1.9 PERFORMANCE MONITORING

A. The Contracting Officer may elect throughout or at any time during the Project to record the number of designers and consultants during the design activities, the number of workers, and construction equipment working on each construction schedule activity in each area of the Project and give a copy of this log to the Contractor. The Contractor shall be responsible for advising the Contracting Officer, without additional cost to the Government, of error in this work history, in writing, within seven (7) calendar days of receipt of same. This information will be used by the Contracting Officer in their evaluation of the adequacy of the Contractor’s performance and project manpower staffing, as well as in the evaluation of Contractor claims.

SCHEDULING OF WORK 01 32 13-18

1. Each week, the Contractor shall submit a “look ahead” report in the form of a bar chart that encompasses all open and planned work activities according to the current Project Schedule, to the Contracting Officer. The minimum timescale definition shall show a four week look ahead period and two weeks behind. The following items shall be clearly marked on the appropriate portion of the current computer produced schedule:

a. Percent Complete.

b. Actual Start/Finish Dates.

c. Bar chart by area (early and late dates with float).

d. Which activities the contractor plans to start or continue during the week.

e. All activities on the critical path.

f. All activities on which have negative float.

2. This “look ahead” report shall serve as a basis for discussions at the project progress meeting. These actual start and finish dates and percentages of completion estimates will, upon verification, be used by the Contracting Officer to record actual progress.

PART 2 - PRODUCTS

2.1 SCHEDULING SOFTWARE

A. The scheduling software used by the Contractor shall be capable of importing/exporting data to/from Primavera Project Planner, most current version. The proposed software shall be capable of transferring the information without degradation in the data, including but not limited to, scheduling logic and sequencing, activities, durations, cost loading, etc.

1. The proposed software shall meet the following minimum criteria.

a. Scheduling:

1) Provide daily scheduling units.

2) Provide independent scheduling calendars.

3) Sort information with a minimum of 36 criteria selections.

SCHEDULING OF WORK 01 32 13-19

4) User defined status.

5) F-S, S-S, F-F, S-F relationships with positive/negative lags.

6) Unlimited projects and target schedules.

7) Dependent or independent sub-project schedule.

8) Provide intelligent alphanumeric activity identifiers - 4 fields.

9) Provide Activity coding: 10 characters in 20 fields.

10) Data and duration constraints.

11) Provide ability to Summarize Master networks.

12) Provide Milestones and flags for constraints.

13) Provide contiguous and interruptible activity scheduling.

14) Provide suspend and resume dates.

15) Provide resource driven durations.

16) Provide Activity, Procurement and Resource/Cost matrix reports.

17) Provide Periodic Performance Data.

18) Provide Automatic Scheduling and Leveling.

19) Provide Progress Spotlight and Update Progress.

b. Resource Management:

1) Unlimited resources per activity and per project.

2) Provide variable resource usage.

3) Prioritized forward and backward leveling and smoothing.

4) Provide hierarchical resource codes.

5) Provide resource lags and durations.

SCHEDULING OF WORK 01 32 13-20

6) Fixed crew size or available staffing resource allocation.

7) Provide resource loading bar charts.

8) Provide nonlinear resource profiles.

9) Provide productivity reporting.

10) Provide internal means for time sheet data entry.

11) Provide resource matrix report.

c. Cost Control:

1) Auto cost: user-definable progress calculations.

2) Variable unit prices over time.

3) 12-character account code including cost type.

4) Wild-card selection and roll-up.

5) Summarize costs.

6) Performance-adjusted cost-to complete calculation.

7) Unit pricing/costing analysis.

8) Cash flow project with payment lag.

9) Earned value analysis.

10) Actual-this-period calculations.

d. Management Graphics:

1) Gantt charts (bar charts).

2) Time-scaled logic diagrams.

3) Pure logic plots.

4) Portrait or landscape orientation.

5) On-screen drawing tools to create lines, boxes, symbols, and logos, and add to text.

6) Early, late and target dates.

SCHEDULING OF WORK 01 32 13-21

7) Progress and critical activities highlighting.

8) Horizontal banding (user-defined sequence).

9) Summary bars.

10) Discrete activities within summary bars.

11) Resource supply and demand curves.

12) Comparative resource application charts.

13) Cash flow curves.

14) Resource requirement graphics.

15) Cash flow and bar chart combination.

16) Import HPGL files from graphics packages.

17) Point size control of lettering.

18) Bar sizing and spacing.

19) Provide multiple arrangements of Activity Columns.

e. Graphic User Interface Features:

1) Create, modify, arrange, personalize networks on screen.

2) Create, store, recall fragnets.

3) Choice of shape and color for activity.

4) Click on activities to define relationships and to edit activity data.

5) Cut, copy, and paste functions.

6) Mark and group functions.

7) Horizontal banding by code.

8) Collapse and explode activity groups.

9) Six levels of zoom plus cosmic view.

10) HTML structure.

SCHEDULING OF WORK 01 32 13-22

11) Hypertext links.

12) Customizable header and footer

2. Reporting:

a. Provide fill-in the blank Custom report writer without a command language to operate.

b. More than 100 standard scheduling, resource, and cost reports.

c. Batch and series reporting.

3. Multiuser Features (for LAN environments):

a. Read-write, read only and exclusive access.

b. File and record-locking.

c. Simultaneous updating, reporting, plotting.

d. Username and password protection.

e. Integrated electronic mail and bulletin board.

f. Network administrative program (NETSET).

PART 3 - EXECUTION (Not used)

END OF SECTION 01 32 13