C109584- Attachment D- Site Specific DIV 1 Specifications.pdf

PROJECT SCHEDULE Page 1 of 15 SECTION 01 32 01

NIH RTPFMB

SECTION 01 32 01

PROJECT SCHEDULE

05/22

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 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;

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Preliminary Project Schedule; G

Initial Project Schedule; G

Design Package Schedule

Periodic Schedule Update; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. Submit to the Contracting Officer for approval an individual who will serve as the Designated Project Scheduler. Include a copy of the candidate’s resume with qualifications. The Designated Project Scheduler must have a minimum of 2-years’ experience scheduling construction projects similar in size, complexity, and nature to this contract with scheduling software that

PROJECT SCHEDULE Page 2 of 15 SECTION 01 32 01 meets the requirements of this specification. The Designated Project Scheduler must have a comprehensive knowledge of CPM scheduling principles and application. The Contracting Officer may remove the Designated Project Scheduler, and require replacement, if the scheduler does not effectively fulfill their duties in accordance with the contract requirements.

PART 2 PRODUCTS

2.1 SOFTWARE

The scheduling software utilized to produce and update the schedules required herein must be capable of meeting all requirements of this specification.

2.1.1 Government Default Software

The Government plans to utilize Microsoft Project or 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.

2.1.2.1 Primavera

Prepare and maintain project schedules using Primavera P6 software (or approved equal) in a version compatible with Government's current version.

Provide the "xer" export file in a version of P6 importable by the Government system.

A listing of Primavera P6 settings and parameters which must be used in preparing the Schedules are contained later in this specification section. Deviation from these settings and parameters, without prior consent of the Contracting Officer, is cause for rejection of schedule submission.

2.1.2.2 Other Than Primavera

If the contractor chooses to utilize an equivalent equal to Primavera P6, Contractor to provide compliance 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.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction design and construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Designers, subcontractors, and suppliers working on the project must also contribute to developing and maintaining an accurate Project Schedule. Provide a schedule

PROJECT SCHEDULE Page 3 of 15 SECTION 01 32 01 that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules. Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN.

3.2.1 Activity Cost Loading

Activity cost loading must be reasonable and without front-end loading.

Evenly disperse overhead and profit to each activity over the duration of the project. 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.

If 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 workdays or 30 calendar days.

3.3.3 Design and Permit Activities

Include design and permit activities with the necessary conferences and follow-up actions and design package submission dates. Include the design schedule in the project schedule, showing the sequence of events involved in carrying out the project design tasks within the specific contract period.

Provide at a detailed level of scheduling sufficient to identify all major design tasks, including those that control the flow of work. Include review and correction periods associated with each item.

PROJECT SCHEDULE Page 4 of 15 SECTION 01 32 01

3.3.4 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.5 Mandatory Tasks

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

a. Submission, review, and acceptance of all Preconstruction submittals (SD-

01).

b. Submission, review, and acceptance of all material submittals with a “G” designation (individual activity for each).

c. Submission, review, and acceptance of design packages.

d. Submission of mechanical/electrical/information systems layout drawings.

e. Long procurement activities.

f. Submission and approval of O & M manuals.

g. Submission and approval of as-built drawings.

h. Submission and approval of New Equipment worksheets.

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

j. Submission of TAB specialist design review report.

k. Submission and approval of fire protection specialist.

l. Submission and approval of Building Commissioning Plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with the contract commissioning requirements. All tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

m. Air and water balancing.

n. Building commissioning - Functional Performance Testing.

o. Controls testing plan submission.

p. Controls testing.

q. Performance Verification testing.

r. Other systems testing, if required.

PROJECT SCHEDULE Page 5 of 15 SECTION 01 32 01

s. Contractor's pre-final inspection.

t. Correction of punch list from Contractor's pre-final inspection.

u. Government's pre-final inspection.

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

w. Final inspection.

3.3.6 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to approvals, acceptance, design reviews, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.7 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited. No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer for approval on a case-by-case basis.

3.3.7.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged.

3.3.7.2 End Project Finish Milestone and Constraint

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

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

3.3.7.3 Interim Completion Dates and Constraints

Constrain contractually specified interim completion dates to show negative float when the calculated late finish date of the last activity in that phase is later than the specified interim completion date.

3.3.7.3.1 Start Phase

Use a start milestone as the first activity for a project phase. Call the

PROJECT SCHEDULE Page 6 of 15 SECTION 01 32 01 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 Seasonal 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-workdays monthly, with the non-workdays selected at random across the weeks of the calendar. Assign non-workdays over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather-related non-workdays to fall on weekends.

3.3.9 Open Ended Logic

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

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

3.3.10 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

3.3.11 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer. Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule.

Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.3.12 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and

PROJECT SCHEDULE Page 7 of 15 SECTION 01 32 01 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

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 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 workdays 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.19 As-Built Drawings

If there is no value designated by a separate contract line item (CLIN) or within the project SOW for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than $20,000 or 1 percent of the present contract value, whichever is greater, up to $200,000.

Activity will be declared 100 percent complete upon the Government's

PROJECT SCHEDULE Page 8 of 15 SECTION 01 32 01 approval.

3.3.20 O & M Manuals

If there is no value designated by a separate contract line item (CLIN) or within the project SOW for O & M manuals, cost load the "Submission and approval of O & M manuals" activity not less than $20,000 or 1 percent of the present contract value, whichever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's approval.

3.3.21 Anticipated Adverse Weather

Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.

3.3.22 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required contract work will be completed before the contractually required completion date.

a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.

b. The Government is under no obligation to accelerate work items it is responsible for to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data, 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

PROJECT SCHEDULE Page 9 of 15 SECTION 01 32 01 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.

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. Include in the design-build schedule detailed design and permitting activities, including but not limited to identification of individual design packages, design submission, reviews, and conferences; permit submissions and any required Government actions; and long lead item acquisition prior to design completion. Also cover in the preliminary design-build schedule the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed construction activities through the dry-in milestone, including all activity coding and cost loading. Include the remaining construction, including cost loading, but it may be scheduled summary in nature. As the design proceeds and design packages are developed, fully detail the remaining construction activities concurrent with the monthly schedule updating process. Constrain construction activities by Government acceptance of associated designs. When the design is complete, incorporate into the then approved schedule update all remaining detailed construction activities that are planned to occur after the dry-in milestone. If applicable, include in the design-build schedule detailed design and permitting activities, including but not limited to identification of individual design packages, design submission, reviews and conferences, permit submissions and any required Government actions, and long lead item acquisition prior to design completion. Also cover in the preliminary design-build schedule the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed construction activities through the dry-in milestone, including all activity coding and cost loading. Include the remaining construction, including cost loading, but it may be scheduled summary in nature. As the design proceeds and design packages are developed, fully detail the remaining construction activities. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.2.1 Design Package Schedule Submission

With each design package submitted to the Government, submit a Fragmentary Network (Fragnet) schedule extracted from the then current Preliminary, Initial or Updated schedule which covers the activities associated with that Design Package including construction, procurement and permitting activities.

3.4.3 Periodic Schedule Updates

Update the Project Schedule on a regular basis, monthly at a minimum or following a Progress Meeting. Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS. These updates will enable the Government to assess Contractor's progress. Update the schedule to include detailed construction activities as the design progresses, but not later than the submission of the final un-reviewed design submission for each separate design package. The Contracting Officer may require submission of detailed

PROJECT SCHEDULE Page 10 of 15 SECTION 01 32 01 schedule activities for any distinct construction that is started prior to submission of a final design submission if such activity is authorized.

a. Update information including Actual Start Dates (AS), Actual Finish

Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the Contractor's

Quality Control Report for an activity start or finish.

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:

3.5.1 Electronic Submission

Provide an electronic copy via email or CD/DVD of the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include the Narrative Report and all required Schedule Reports. 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 workdays.

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

The format, filtering, organizing, and sorting for each schedule report will

PROJECT SCHEDULE Page 11 of 15 SECTION 01 32 01 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. 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: 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.

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.

PROJECT SCHEDULE Page 12 of 15 SECTION 01 32 01

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 Work Breakdown Structure (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. 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 workdays after the periodic schedule update meeting.

3.7 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled PERIODIC SCHEDULE UPDATE MEETINGS for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks. Use the current approved schedule update for the purposes of this meeting and for the production and

PROJECT SCHEDULE Page 13 of 15 SECTION 01 32 01 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

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.

PROJECT SCHEDULE Page 14 of 15 SECTION 01 32 01

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 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 workdays, 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 considered for the exclusive use of either the Government or the Contractor including activity and/or project float. Activity float is the number of workdays that an activity can be delayed without causing a delay to the "End Project" finish milestone. Project float (if applicable) is the number of workdays between the projected early finish and the contract completion date milestone.

PROJECT SCHEDULE Page 15 of 15 SECTION 01 32 01

3.11 PRIMAVERA P6 MANDATORY REQUIREMENTS

Utilizing Primavera P6 (or approved equal), the following settings are mandatory and required in all schedule submissions to the Government:

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

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

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

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

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

8.0 Hour days.

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

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

Logic".

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

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

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

-- End of Section --

SUBMITTAL PROCEDURES Page 1 OF 21 SECTION 01 33 00

SECTION 01 33 00

SUBMITTAL PROCEDURES

The Contracting Officer may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective project statement of work.

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

Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

Contractor's Quality Control (CQC) Manager and the Designer of Record, if applicable, shall check and approve all items prior to submittal and stamp, sign, and date indicating action taken. Proposed deviations from the contract requirements are to be clearly identified. Include within submittals items such as: Contractor's, manufacturer's, or fabricator's drawings; descriptive literature including (but not limited to) catalog cuts, diagrams, operating charts or curves; test reports; test cylinders;

samples; O&M manuals (including parts list); certifications; warranties;

and other such required submittals.

Submittals requiring Government approval shall be provided prior to the acquisition of the material or equipment covered thereby. All materials shall be picked up and disposed of in accordance with manufacturer's Material Safety Data Sheets (MSDS)/Safety Data Sheet (SDS) and in compliance with existing laws and regulations. Samples remaining upon completion of the work shall be stored in accordance with manufacturer’s MSDS/SDS and in compliance with existing laws and regulations.

1.1 DEFINITIONS

1.1.1 Submittal Descriptions (SD)

Submittal requirements are specified in the project statement of work or applicable technical sections. Submittals are identified by Submittal Description (SD) numbers and titles as follows:

Submittals which are required prior to an award commencing work on site. Submittals required prior to the start of the next major phase of the construction on a multi-phase contract. Schedules or tabular list of data or tabular list including location, features, or other pertinent information regarding products, materials, equipment, or components to be used in the work, submitted prior to contract notice to proceed or next major phase of construction.

SUBMITTAL PROCEDURES Page 2 OF 21 SECTION 01 33 00

Certificates of insurance

Surety bonds

List of proposed subcontractors

List of proposed products

Construction Progress Schedule

Network Analysis Schedule (NAS)

Submittal register

Schedule of prices

Health and safety plan

Work plan

Quality Control(QC) plan

Accident Prevention Plan

Construction Site Plan

Traffic Control Plan

SD-02 Shop Drawings

Drawings, diagrams and schedules specifically prepared to illustrate some portion of the work.

Diagrams and instructions from a manufacturer or fabricator for use in producing the product and as aids to the Contractor for integrating the product or system into the project.

Drawings prepared by or for the Contractor to show how multiple systems and interdisciplinary work will be coordinated.

SD-03 Product Data

Catalog cuts, illustrations, schedules, diagrams, performance charts, instructions and brochures illustrating size, physical appearance and other characteristics of materials, systems or equipment for some portion of the work.

Samples of warranty language when the contract requires extended product warranties.

SD-04 Samples

Fabricated or unfabricated physical examples of materials, equipment or workmanship that illustrate functional and aesthetic characteristics of a material or product and establish standards by which the work can be judged.

SUBMITTAL PROCEDURES Page 3 OF 21 SECTION 01 33 00

Color samples from the manufacturer's standard line (or custom color samples if specified) to be used in selecting or approving colors for the project.

Field samples and mock-ups constructed on the project site establish standards by which the ensuring work can be judged. Includes assemblies or portions of assemblies which are to be incorporated into the project and those which will be removed at conclusion of the work.

SD-05 Design Data

Design calculations, mix designs, analyses or other data pertaining to a part of work.

SD-06 Test Reports

Report signed by authorized official of testing laboratory that a material, product, or system identical to the material, product or system to be provided has been tested in accord with specified requirements. (Testing must have been within three years of date of contract award for the project.)

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

Report which includes finding of a test made at the job site or on sample taken from the job site, on portion of work during or after installation.

Investigation reports.

Daily logs and checklists.

Final acceptance test and operational test procedure.

SD-07 Certificates

Statements printed on the manufacturer's letterhead and signed by responsible officials of manufacturer of product, system or material attesting that product, system or material meets specification requirements. Must be dated after award of contract and clearly name the project.

Document required of Contractor, or of a manufacturer, supplier, installer or subcontractor through Contractor, the purpose of which is to further quality of orderly progression of a portion of the work by documenting procedures, acceptability of methods or personnel qualifications.

Confined space entry permits.

Text of posted operating instructions.

SD-08 Manufacturer's Instructions

Preprinted material describing installation of a product, system or

SUBMITTAL PROCEDURES Page 4 OF 21 SECTION 01 33 00 material, including special notices and Material Safety Data sheets concerning impedances, hazards and safety precautions.

SD-09 Manufacturer's Field Reports

Documentation of the testing and verification actions taken by manufacturer's representative at the job site, in the vicinity of the job site, or on a sample taken from the job site, on a portion of the work, during or after installation, to confirm compliance with manufacturer's standards or instructions. The documentation must be signed by an authorized official of a testing laboratory or agency and must state the test results; and indicate whether the material, product, or system has passed or failed the test.

Factory test reports.

SD-10 Operation and Maintenance Data

Data that is furnished by the manufacturer, or the system provider, to the equipment operating and maintenance personnel, including manufacturer's help and product line documentation necessary to maintain and install equipment. This data is needed by operating and maintenance personnel for the safe and efficient operation, maintenance, and repair of the item.

This data is intended to be incorporated in an operations and maintenance manual or control system.

SD-11 Closeout Submittals

Documentation to record compliance with technical or administrative requirements or to establish an administrative mechanism.

Special requirements necessary to properly close out a project. For example, Record Drawings, As-built Drawings, and Equipment Data Sheets.

1.1.2 Approving Authority

Office or designated person authorized to approve submittal.

1.1.3 Work

As used in this section, on- and off-site construction required by contract documents, including labor necessary to produce submittals, construction, materials, products, equipment, and systems incorporated or to be incorporated in such construction.

1.2 SUBMITTALS

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with this section.

SUBMITTAL PROCEDURES Page 5 OF 21 SECTION 01 33 00

Submittal Register; G

1.3 SUBMITTAL CLASSIFICATION

Submittals are classified as follows:

1.3.1 Designer of Record Approved (DA)

Designer of Record approval is required for extensions of design, critical materials, any deviations from the solicitation, the accepted proposal, or the completed design, equipment whose compatibility with the entire system must be checked, and other items as designated by the Contracting Officer. Within the terms of the Contract Clause entitled "Specifications and Drawings for Construction," they are considered to be "shop drawings." Contractor to provide the Government with the number of copies designated hereinafter of all Designer of Record approved submittals. The Government may review any or all Designer of Record approved submittals for conformance to the Solicitation and Accepted Proposal. The Government will review all submittals designated as deviating from the Solicitation or Accepted Proposal, as described below. Generally, design submittals should be identified as SD-05 Design Data submittals.

1.3.2 Government Approved (G)

Government approval is required for extensions of design, critical materials, deviations, equipment whose compatibility with the entire system must be checked, and other items as designated by the Contracting Officer. Government approval is required for any deviations from the Solicitation or Accepted Proposal and other items as designated by the Contracting Officer. Within the terms of the Contract Clause entitled "Specifications and Drawings for Construction," they are "shop drawings."

1.3.3 Designer of Record Approved/Government Approved (DA/GA)

Design of Record approval and Government Approval is required as designated by the Contracting Officer.

1.3.4 Information Only (FIO)

Submittals not requiring Government approval will be for information only. For Design-build construction all submittals not requiring Designer of Record or Government approval will be for information only. They are not considered to be "shop drawings" within the terms of the Contract Clause referred to above.

1.4 NOT USED

1.5 PREPARATION

1.5.1 Accessibility Requirements

All transmittal information prepared by the Contractor shall be Section 508

SUBMITTAL PROCEDURES Page 6 OF 21 SECTION 01 33 00 compliant for accessibility to people with disabilities. Submittal content originating from vendor or supplier resources shall be in original format and free of scanned images of text.

1.5.2 Transmittal Form

Transmit each submittal, except sample installations and sample panels to office of the approving authority. Transmit submittals with transmittal form prescribed by Contracting Officer and standard for project. On the transmittal form identify Contractor, indicate date of submittal, and include information prescribed by transmittal form and required in paragraph entitled "Identifying Submittals." Process transmittal forms to record actions regarding sample(s), installation(s), panel(s).

Use Transmittal Form (ENG Form 4025) for submitting both Government approved and information only submittals in accordance with the instructions on the reverse side of the form. These forms will be furnished to the Contractor. Properly complete this form by filling out all the heading blank spaces and identifying each item submitted.

Exercise special care to ensure proper listing of the specification paragraph and sheet number of the contract drawings pertinent to the data submitted for each item.

1.5.3 Identifying Submittals

When submittals are provided by a lower tier contractor the Prime Contractor is to prepare, review and stamp with Contractor's approval all specified submittals prior to submitting for Government approval.

Identify submittals, except sample installations and sample panels, with the following information permanently adhered to or noted on each separate component of each submittal and noted on transmittal form. Mark each copy of each submittal identically, with the following:

a. Project title and location.

b. Construction contract number

c. Date of the drawings and revisions.

d. Name, address, and telephone number of subcontractor(s), supplier, manufacturer and any other second tier Contractor associated with submittal.

e. Section number of the specification section by which submittal is required.

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

g. When a resubmission, add alphabetic suffix on submittal description, for example,…