80KSC021R0029 J-F Technical Specification K0000434325-SPC.pdf

A

Export Control Notice

Comment: EAR 99 -- NO LICENSE REQUIRED

This information or item is controlled under the Export Administration Regulations (EAR) as EAR99. It may be exported without a license, except to countries subject to embargoes and other special controls or general prohibitions per 15 CFR Parts 736 and 746. The designation of EAR99 does not constitute public release.

Reference EDR Log #: 9148 NASA KSC Export Control Office, 321-867-9209

Signature Certification

Project Title:

Project Control Number:

Project Drawing Number:

Project Specification Number:

Project Data Manual Number:

Discipline Name ST License No. Signature

NASA Approvals

Discipline Name Signature

Technical Specification for EES for SLS K0000434325-SPC

EES for SLS Vehicles 98967 K0000151046, K0000141041, et al.

K0000434325-SPC

KSC-NE-15113 / KSC-NE-15112

Mechanisms Bradford P. Lytle FL 36121

Environmental Ben Chandler FL 2246

Mechanical Fluids John A. McMillin FL 24576

Mechanical Ned Hansen UT 165888

Architectural Alice M. Schultz FL 15811

Mechanical Alan C. Littlefield FL 46649

Electrical Daniel J. Vigeant FL 75981

Coatings Paula K. Endicott FL 73787

Architectural Environmental Michael T. Barth II

Electrical

Materials & Processes

Mechanical

Structural

Structural

Controls

NASA Design Manager

NASA Project Manager

NASA Branch Manager

Dung H. Trang

Eliza Montgomery

Jeremy E. Porta

Kailey Younkin

Samantha Testa

Timothy Reardon

Michael T. Barth II

Lori N. Jones

Scott M. Hunt

SENSITIVE BUT UNCLASSIFIED

TECHNICAL SPECIFICATION FOR EES FOR SLS K0000434325-SPC

PROJECT TABLE OF CONTENTS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 11 00 01 32 01.00 10 01 33 00 01 42 00 01 45 00.00 40 01 57 19 01 78 23 01 91 00.15 10

DI VI SI ON 05 - METALS

05 50 14

DI VI SI ON 09 - FI NI SHES

09 97 30.30 98

DI VI SI ON 40 - PROCESS I NTERCONNECTI ONS

40 60 00

DI VI SI ON 41 - MATERI AL PROCESSI NG AND HANDLI NG EQUI PMENT

41 22 23

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 3

SENSITIVE BUT UNCLASSIFIED

SUMMARY OF WORK

PROJECT SCHEDULE

SUBMITTAL PROCEDURES

SOURCES FOR REFERENCE PUBLICATIONS

QUALITY CONTROL

TEMPORARY ENVIRONMENTAL CONTROLS

OPERATION AND MAINTENANCE DATA

EMERGENCY EGRESS SYSTEM COMMISSIONING

STRUCTURAL METAL FABRICATIONS

PROTECTIVE COATING OF STEEL ON GROUND

SUPPORT EQUIPMENT

PROCESS CONTROL

EMERGENCY EGRESS SYSTEM (EES) HOISTS

AND WINCHES

SECTION 01 11 00

SUMMARY OF WORK

08/15

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work to be performed under this project consists of providing the labor, equipment, and materials for the design, fabrication, installation , testing and commissioning of the Emergency Egress System (EES) conveyance. The work includes fabrication and assembly of: Baskets;

Cables; Cable Puller; Clamp Brakes; Sheaves; and design, fabrication, and assembly of four (4) wire rope tensioning skid assemblies which include a winch, hydraulic tensioner and necessary controls; and four (4) synthetic rope pilot line hoists with two (2) portable control panels .

This equipment will be used for the safe evacuation of crew from ML-1 Level 274 and involves the installation and removal of EES Track Cables.

The work to be performed under this project includes structural, mechanical, electrical, and coatings, and consists of assembly, shop testing, shipment to project site and acceptance testing including demonstration of track cable installation and removal as complete commissioning of the EES subsystem.

1.1.2 Location

The work is located at Launch Complex 39 Pad B , at the Kennedy Space Center, Florida.

1.2 CONTRACT DRAWINGS

The following drawings accompany this specification and are a part thereof.

Drawing K0000151040 EES Drawing Key sheets 1 through 5;

Drawing K0000151041 EES Setup and Arrangement with K0000151042 Setup Kit, EES and associated parts, (total 9 sheets);

Drawing K0000154712 EES Sheave Installation with K0000151044 EES Sheave Installation Kit, and K0000151045 EES Terminus Sheave Assembly with associated parts, (total 15 sheets);

Drawing K0000151046 EES Basket Assembly with associated parts (total 522 sheets);

Drawing K0000151047 Cable Puller and Weights Assembly with associated parts, (total 24 sheets);

Drawing K0000151048 EES Clamp Brake Assembly with associated parts, (total 18 sheets); and

Drawing K0000154713 Pilot Line Hoist Installation with K0000154714 Pilot Line Hoist Installation Kit, (total 3 sheets).

SECTION 01 11 00 Page 4

1.3 OCCUPANCY OF PREMISES

Launch Complex 39B , Mobile Launcher Park Site and VAB Highbay 3 will be occupied by seperate but concurrent contracts during performance of work under this Contract.

Before work is started, arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 5

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

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

1.2 SUBMITTALS

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

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

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications ; G

Preliminary Project Schedule ; G

Initial Project Schedule ; G

Periodic Schedule Update ; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The authorized representative must have a minimum of 5-years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. Representative must have a comprehensive knowledge of CPM scheduling principles and application.

The representative must identify successful performance of CPM scheduling for at least two (2) projects similar in size and nature that they have supported as project scheduler in the past 5-years that required compliance with a past or current version of UFGS Section 01 32 01.00 10 .

The representative can be an employee of the contractor or subcontracted.

When a subcontractor will be the scheduling representative, identify the capabilities of the subcontractor company for CPM scheduling and the personnel who will perform the scheduler role if more than one person could possibly be assigned. When a subcontractor will be the scheduling representative, the services must include addressing all scope of this

SECTION 01 32 01.00 10 Page 6 specification section as bid, including the potential for time impact analyses related to scope changes or when addressing delay by the Government.

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 intends to use Primavera P6 , exclusively .

2.1.2 Contractor Software

Scheduling software used by the contractor must be Primavera P6.

2.1.2.1 Primavera

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

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts and Contract Clause J-A-6 . 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 and shall include any additive work introduced in the contract through a contract modification . The scheduling of construction is the responsibility of the Contractor. Features of work for which the contractor has design responsibility shall be included in the schedule. Contractor management personnel must actively participate in its development. Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules. Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract line item number, CLIN, must equal the value of the CLIN. This is also applicable to any additive work introduced in the contract via a contract modification.

3.2.1 Activity Cost Loading

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

Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer. Pre-Construction submittals and

SECTION 01 32 01.00 10 Page 7 contractor procurement activities shall not be cost loaded, with the exception of "Delivery" activities. Labor and material costs shall be separated for those schedule activities that include both labor and materials costs. A stored materials log shall be prepared and maintained by the contractor for any delivery items that are cost loaded. Contracting Officer reserves the final authority of approving payment for stored materials. Major milestones shall not be cost loaded unless otherwise approved 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 schedule , initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

Less than 2 percent of all non-procurement activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

3.3.3 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.3.4 Mandatory Tasks

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

a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each).

b. Submission, review and approval of required submittals including riveting plan, per Section 05 50 14 STRUCTURAL METAL FABRICATIONS.

SECTION 01 32 01.00 10 Page 8

c. Long procurement activities .

d. Fabrication durations for all components .

e. Mandatory Inspection Points (MIPs) .

f . Erection/Installation durations of all components .

g. System Testings Tasks and Durations, including EES Test Plan, per Section 01 91 00.15 10 EMERGENCY EGRESS SYSTEM COMMISSIONING; welding process, per Section 05 50 14 STRUCTURAL METAL FABRICATIONS; Software Design Reviews, per Section 40 60 00 ; and Test Matrix, per Section

41 22 23 EES HOISTS AND WINCHES.

h. System Commissioning designating Installation/Assembly, Performance Testing & Acceptance Testing line items .

i . ML availablility at the Pad .

j . Submission and approval of the EES Test Plan , test data, and reports:

Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with KSC-NE-15114 Commissioning Plan requirements. All tasks associated with all testing and commissioning will be completed prior to submission of commissioning re cord and subsequent contract completion.

k. Controls testing plan submission.

l . Controls testing.

m. Other systems testing, if required.

n. Contractor's pre-final inspection.

o. Contractor Punch List .

p. Government's pre-final inspection.

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

r . Final inspection.

3.3.5 Government Activities

Show Government and other agency activities that could impact progress.

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

3.3.6 Standard Activity Coding Dictionary

Activity codes shall be assigned as applicable to the schedule activities:

CLIN, CSI, SOV, Phase, Area, Responsibility, Workers Per Day. Other codes can be assigned as well. Contractor shall provide a "Dictionary" of all activity codes used on the schedule.

SECTION 01 32 01.00 10 Page 9

3.3.6.1 Workers Per Day (WRKP)

Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

3.3.6.2 Responsible Party Coding (RESP)

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record);

ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE).

3.3.6.3 Modification Number (MODF)

Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.3.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. The project Details shall include a "must finish by" constraint, which shall reflect the contractual completion date based on the project period of performance (POP). The POP shall include government issued down-days as defined in the contract, this down days shall be loaded at the end of the schedule.

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."

SECTION 01 32 01.00 10 Page 10

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

3.3.7.3 Interim Completion Dates and Constraints

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

3.3.7.3.1 Start Phase

Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work.

3.3.7.3.2 End Phase

Use a finish milestone as the last activity for a project phase. Call the finish milestone "End Phase X" where "X" refers to the phase of work.

3.3.8 Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop 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-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated adverse weather delay work days provided in the Special Contract Clauses. Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends .

3.3.9 Open Ended Logic

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

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

3.3.10 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish

SECTION 01 32 01.00 10 Page 11

(AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

3.3.11 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer.

Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.3.12 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.

3.3.13 Original Durations

Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.

3.3.14 Leads, Lags, and Start to Finish Relationships

Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

b. Start to Finish (SF) relationships are prohibited.

3.3.15 Retained Logic

Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(s) starts and the predecessor activity(s) has not finished (out-of-sequence progress). Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") are not be allowed.

3.3.16 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management.

3.3.17 Remaining Duration

Update the remaining duration for each activity based on the number of

SECTION 01 32 01.00 10 Page 12 estimated work days it will take to complete the activity. Remaining duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete.

3.3.18 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the present contract value. Activity(ies) may be declared 100 percent complete upon the Government's verification of completion and correction of all punch list work identified during Government pre-final inspection(s).

3.3.18.1 As-Built Drawings

If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than $35,000 or 1 percent of the present contract value, which ever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's approval.

3.3.18.2 O & M Manuals

Cost load the "Submission and approval of O & M manuals" activity not less than $20,000. Activity will be declared 100 percent complete upon the Government's approval of all O & M manuals.

3.3.19 Anticipated Adverse Weather

Paragraph applicable to contracts with clause entitled TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.

3.3.20 Early Completion Schedule and the Right to Finish Early

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

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

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

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.

Review comments made by the Government on the schedule(s) do not relieve the Contractor from compliance with requirements of the Contract Documents.

SECTION 01 32 01.00 10 Page 13

3.4.1 Preliminary Project Schedule Submission

Within 30 calendar days after the Notice of Award (NOA) 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 Pre-work meeting (or pre-construction meeting) . Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities.

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 30 calendar days after unrestricted 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 schedule detailed design, review, approval, and construction activities, including but not limited to, the delegated engineering tasks. 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 design. When the design is complete incorporate into the then approved schedule, update all remaining detailed construction activities that are planned to occur. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Periodic Schedule Updates

Update the Project Schedule on a regular basis, monthly at a minimum.

Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS. These updates will enable the Government to assess Contractor's progress.

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.

3.5 SUBMISSION REQUIREMENTS

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

SECTION 01 32 01.00 10 Page 14

3.5.1 Data CD/DVDs

Provide two sets of data CD/DVDs containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include on the data CD/DVDs the Narrative Report and all required Schedule Reports. Label each CD/DVD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule must have a unique file name and use project specific settings.

3.5.2 Narrative Report

Provide a Narrative Report with each schedule submission. The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for any problems, either current or potential, which are revealed through that analysis.

Include the following information as minimum in the Narrative Report:

a. Identify and discuss the work scheduled to start in the next update period.

b. A description of activities along the two most critical paths where the total float is less than or equal to 20 work days.

c. A description of current and anticipated problem areas or delaying factors and their impact and an explanation of corrective actions taken or required to be taken.

d. Identify and explain why activities based on their calculated late dates should have either started or finished during the update period but did not.

e. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, lag changes, resource changes, and actual start and finish date changes.

f. Identify and discuss out-of-sequence work.

g. Additional reports may be requested by the Government at no additional cost to the Government throughout the entire project POP until Project Completion.

3.5.3 Schedule Reports

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer. Typically, reports contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format.

Provide 3 sets of hardcopy reports. The following lists typical reports that will be requested:

3.5.3.1 Activity Report

List of all activities sorted according to activity number.

SECTION 01 32 01.00 10 Page 15

3.5.3.2 Logic Report

List of detailed predecessor and successor activities for every activity in ascending order by activity number.

3.5.3.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.

3.5.3.4 Earnings Report by CLIN

A compilation of the Total Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

3.5.3.5 Schedule Log

Provide a Scheduling/Leveling Report generated from the current project schedule being submitted.

3.5.3.6 Additional Schedule Items

Initial Project Schedule and Monthly Reports shall also include: Near Critical activities, 1 Month look ahead, Claim Digger/Comparison Report.

Additional reports may be requested by the Government at no additional cost to the Government throughout the entire project POP until Project Completion.

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.

SECTION 01 32 01.00 10 Page 16

3.5.4.3 Critical Path

Show all activities on the critical path. The critical path is defined as the longest path.

3.5.4.4 Banding

Organize activities using the WBS or as otherwise directed to assist in the understanding of the activity sequence. Typically, this flow will group activities by major elements of work, category of work, work area and/or responsibility.

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

With each schedule submission, provide a SVC diagram showing 1) Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates, and 2) Earned Value to-date.

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

Conduct periodic schedule update meetings for the purpose of reviewing the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and progress payment. Conduct meetings at least monthly within five days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows all meeting participants to view the proposed schedule during the meeting. The Contractor's authorized scheduler must organize, group, sort, filter, perform schedule revisions as needed and review functions as requested by the Contractor and/or Government. The meeting is a working interactive exchange which allows the Government and Contractor the opportunity to review the updated schedule on a real time and interactive basis. The meeting will last no longer than 8 hours. Provide a draft of the proposed narrative report and schedule data file to the Government a minimum of two workdays in advance of the meeting. The Contractor's Project Manager and scheduler must attend the meeting with the authorized representative of the Contracting Officer. Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work.

Following the periodic schedule update meeting, make corrections to the draft submission. Include only those changes approved by the Government in the submission and invoice for payment.

3.6.2 Update Submission Following Progress Meeting

Submit the complete Periodic Schedule Update of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 work days after the periodic schedule update meeting.

3.6.3 Periodic Schedule Update

Periodic schedule updates should be from the 1st day of the month to the last day of the month by Close of Business (COB). The Data Date (DD) should be set to the last day of the month COB.

3.6.4 Monthly Schedule Update

Each monthly schedule update shall have as a base previous month approved

SECTION 01 32 01.00 10 Page 17 schedule.

3.6.5 Draft Schedule Update

The draft schedule update shall be submitted to the Government one week before the completion of the month (site-walk and draft review) and the review meeting will be scheduled on the first work day of the following month. Example: For the schedule Update DD31-Oct-17 the draft copy to be submitted on 24-Oct-17, schedule update meeting to be scheduled on 1-Nov-17, and Complete and Final Package to be submitted on 5-Nov-17.

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 review of reports. At the weekly progress meeting, address the status of RFIs, RFPs and Submittals.

3.7.1 Two to Four Week Look-Ahead Schedule

Contractor shall prepared a two to four week “look-ahead schedule” in support of the “REGULARLY SCHEDULED STATUS MEETINGS” as called out in J-B-16. This look ahead schedule should be tied back to the main project schedule using some activities as “anchor points”, additional detail shall be provided for the look-ahead schedule for better planning. Additional Details shall include the following at minimum:

Anticipated Lifts Potential Outages Modifications of Traffic Mandatory Inspections Points Upcoming Testing

Concrete Pours Major Equipment Installation by area

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. All approved contract Modifications (MODs) shall be included in the schedule under 'Modifications' WBS. The MODs activity shall comply with activity requirements of the baseline schedule and shall be coded.

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

SECTION 01 32 01.00 10 Page 18 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.

Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay will not be a cause for an extension to the performance period, completion date, or any interim milestone date.

3.8.6 Impact to Early Completion Schedule

No extended overhead will be paid for delay prior to the original Contract Completion Date for an Early Completion IPS unless the Contractor actually performed work in accordance with that Early Completion Schedule. The Contractor must show that an early completion was achievable had it not been for the impact.

3.8.7 Concurrent Delays

If concurrent contractor delays are identified in the schedule they will be subtracted from the total time extension request (based on the delay fragnet). The Government may request to insert the delay fragnet in the current schedule update for additional analysis, if needed, to determine

SECTION 01 32 01.00 10 Page 19 the impact effect to date; a time extension request package shall also include the .xer files for Government analysis.

3.8.8 Approved Modifications

All the approved Modifications (MODs) shall be included in the schedule under ‘Modifications’ WBS. The MODs activity shall comply with activity requirements and shall be coded.

3.9 FAILURE TO ACHIEVE PROGRESS

Should the progress fall behind the approved project schedule for reasons other than those that are excusable within the terms of the contract, the Contracting Officer may require provision of a written recovery plan for approval. The plan must detail how progress will be made-up to include which activities will be accelerated by adding additional crews, longer work hours, extra work days, etc.

3.9.1 Artificially Improving Progress

Artificially improving progress by means such as, but not limited to, revising the schedule logic, modifying or adding constraints, shortening activity durations, or changing calendars in the project schedule is prohibited. Indicate assumptions made and the basis for any logic, constraint, duration and calendar changes used in the creation of the recovery plan. Any additional resources, manpower, or daily and weekly work hour changes proposed in the recovery plan must be evident at the work site and documented in the daily report along with the Schedule Narrative Report.

3.9.2 Failure to Perform

Failure to perform work and maintain progress in accordance with the supplemental recovery plan may result in an interim and final unsatisfactory performance rating and 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 work days that an activity can be delayed without causing a delay to the "End Project" finish milestone. Project float (if applicable) is the number of work days between the projected early finish and the contract completion date milestone. Float is not exclusively calculated in calendar days, but based on the respective activity assigned calendar. It is recommended to assign to the project a 7-day calendar (project details) so the OD/RD/TF on WBS level 1 are calculated in calendar days.

SECTION 01 32 01.00 10 Page 20

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

Import the schedule data into the Quality Control System (QCS) and export the QCS data to the Government. This data is considered to be additional supporting data in a form and detail required by the Contracting Officer pursuant to FAR 52.232-5 Payments under Fixed-Price Construction Contracts. The receipt of a proper payment request pursuant to FAR 52.232-27 Prompt Payment for Construction Contracts is contingent upon the Government receiving both acceptable and approvable hard copies and matching electronic export from QCS of the application for progress payment.

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

If Primavera P6 is being used, request a backup file template (.xer) from the Government, if one is available, prior to building the schedule. 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.

k. Each activity shall have a unique name and area designator (if applicable). Example: 'Install Elec R/I - NEB Level 1'

l. Budgeted costs and At completion costs shall be equal at all times.

Resource assignment shall be set to 'Subract Actual from At completion'. This setting is for Fixed-price project.

m. Budgeted units and At completion units value should match Budgeted costs and At completion costs. (Example: Budgeted units 1,000 and Budgeted costs $1,000).

n. Activities calculations shall be set to "Link Budget and At Completion for activities not started'.

SECTION 01 32 01.00 10 Page 21

o. The Total Float calculation setting should be set to 'Late Finish - Early Finish'.

-- End of Section --

SECTION 01 32 01.00 10 Page 22

SECTION 01 33 00

SUBMITTAL PROCEDURES

08/18

PART 1 GENERAL

1.1 SUMMARY

1.1.1 Submittal Information

The Contracting Officer may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections. Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

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

1.1.2 Project Type

The Contractor's Quality Control (CQC) System Manager shall check and approve all items before 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.

The Contractor and the Designer of Record (DOR), if applicable, are to check and approve all items before 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.

1.1.3 Submission of Submittals

Schedule and provide submittals requiring Government approval before acquiring the material or equipment covered thereby. Pick up and dispose of samples not incorporated into the work in accordance with manufacturer's Safety Data Sheets (SDS) and in compliance with existing laws and regulations.

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

Submittal requirements are specified in the technical sections. Examples and descriptions of submittals identified by the Submittal Description (SD) numbers and titles follow:

SECTION 01 33 00 Page 23

SD-01 Preconstruction Submittals

Submittals that are required prior to or commencing with the start of work on site. Submittals that are required prior to or at the start of construction (work) or the next major phase of the construction on a multiphase contract.

Preconstruction Submittals include schedules and a tabular list of locations, features, and other pertinent information regarding products, materials, equipment, or components to be used in the work.

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

Product data shall include salient features and ratings that are applicable to design and as specified herein. They shall be provided for all assemblies and subassemblies including but not limited to the following

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-05 Design Data

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

SD-06 Test Reports

Report that includes findings of a test required to be performed on an actual portion of the work or prototype prepared for the project before shipment to job site , and testing required for final acceptance at the job site .

Daily logs and checklists

Shop test procedure

Final…