Project Controls Specification Summary

The following includes some information about the anticipated project control requirements of the construction contractor and the duties of the Consultant acting on UDOTs behalf as the Engineer. This is provided to highlight some new project controls methods UDOT will incorporate into the project of which the Consultant should become familiar.

DEFINITIONS Critical Path: The series of activities that determine the projects substantial completion date; a delay to any of these activities could delay the finish date of the entire project. The Department defines the Critical Path as the Longest Path. Critical Path Method (CPM): The method by which activity durations and the relationships between activities are used to mathematically calculate a schedule for the entire project which focuses on the Critical Path activities that affect the completion of the project. Time Impact Analysis (TIA): A schedule or schedule fragnet, and narrative report developed specifically to demonstrate what affect a proposed change or delay has on the current scheduled project substantial completion date. Total Float: The difference between the earliest and latest allowable start or finish times for an activity which generally represents the amount of time an activity can be delayed without delaying the project substantial completion date. Work Breakdown Structure (WBS): A hierarchy of work that must be accomplished to complete the project. It is structured in levels of work detail that describe the project and identifiable work elements.

PROGRESS PAYMENTS Prior to payment, the Engineer requires documentation according to UDOT Specifications to substantiate acceptance of materials and work items for both quality and quantity. As approved by the Engineer, payment for work performed on a unit or measured basis may be released up to 90 percent of the value of the quantity associated with the schedule activity while documentation is in the process of being received and substantiated by the Engineer. The remaining 10 percent of the value will be paid when the work is complete AND all required documentation is received and substantiated by the Engineer.

The Engineer cannot approve payment prior to receiving documentation when such documentation is required by contract prior to placement of materials (i.e., material certifications, FHWA requirement, Buy America, etc.). As approved by the Engineer, partial payment for work performed on a lump sum or plan quantity activity may be released as follows: a. Payment may be released at 50 percent of the activity value when the physical progress of an activity is at least 50 percent achieved and accepted according to Contract requirements. b. Payment may be released at 90 percent of the activity value when the physical progress of an activity is 100 percent achieved and accepted according to Contract requirements, and documentation is in the process of being received and substantiated by the Engineer. The remaining 10 percent of the value will be paid when the work is complete AND all required documentation is received and substantiated by the Engineer. Level-of-effort activities associated with project management are paid on a percentage basis according to monthly schedule progress. At no time are dates or durations in the construction schedule to be altered or manipulated for payment purposes. All schedule activities are to be updated according to progress in the field and reflect accurate as-built information in accordance with contract requirements. See Section 00555S.

QUALIFIED SCHEDULER A. Provide a qualified scheduler who has a minimum of three years experience performing the duties of planning, developing, evaluating, analyzing, maintaining and reporting Critical Path Method (CPM) schedules, and possesses demonstrated proficiency in CPM schedule methodology and utilization of Primavera P6 software, or current version. The Contractors project manager is not allowed to perform the role of qualified scheduler.

BASELINE CONSTRUCTION SCHEDULE A. Baseline Schedule Pre-Submittal Meeting 1. Conduct a pre-submittal schedule meeting to: a. Review the requirements of this section prior to submittal of the baseline construction schedule. b. Determine estimate period closing dates upon which the monthly schedule updates and progress payments will be generated (with approval of the Engineer). 2. Attendees to include, at a minimum, the Contractors project manager, Contractors qualified scheduler, and the Engineer.

3.

The Contractor may arrange this meeting prior to Notice to Proceed to facilitate timely development of the baseline schedule.

B.

General Requirements 1. Provide the Engineer with a baseline construction schedule meeting the requirements of this section using Primavera 6.0 or current version or Primavera Contractor. Provide a schedule narrative as described in this section. 2. Reflect the proposed approach to accomplish the work. 3. Use the baseline schedule to coordinate all activities on the project, including those with other entities such as subcontractors, vendors and suppliers, utilities, local governments, special service districts, and the Department. 4. Employ a sufficient workforce, supply adequate materials and equipment, and progress the work with such diligence as to maintain the rate indicated in the accepted baseline construction schedule. 5. All costs to maintain the schedule are solely the Contractors obligation and at no expense to the Department. Baseline Schedule Submission 1. Establish a sequential numbering system for schedule submittals and associated reports to allow easy identification of Baseline Schedule(s), Schedule Updates, and Schedule Update resubmissions,as acceptable to the Engineer. 2. Submit to the Engineer a baseline construction schedule with schedule narrative within 7 calendar days of the Notice to Proceed in a format acceptable to the Engineer, to include: a. One electronic copy of Primavera software file (.XER file). b. Two hard copies and one electronic copy of narrative report. c. Two hard copies and one electronic (PDF file) copy of layouts as generated from Primavera, as outlined in the Baseline Schedule Narrative Requirements in this section. 3. The Engineer reviews the baseline schedule and returns it as accepted, accepted with comments, or returned with comments for resubmission within 10 working days from the date of receipt. a. The Contractor addresses comments and revises the schedule as necessary to the satisfaction of the Engineer. 4. The Contractor completes the final baseline schedule, incorporating any revisions necessary, and obtains Engineers acceptance within 30 calendar days from Notice to Proceed. 5. No progress payments are made before the Engineer accepts the final baseline schedule. 6. The Contractor is solely responsible for planning and executing the work. Engineers acceptance of the baseline schedule does not:

C.

7.

8.

Imply approval of any construction methods or relieve the Contractors responsibility to provide sufficient materials, equipment, and labor to guarantee completion of the project in accordance with the Contract. b. Attest to the validity of assumptions, activities, relationships, sequences, resource allocations, or any other aspect of the baseline construction schedule. Failure to include any element of work required by the contract in the accepted baseline construction schedule does not relieve the Contractors responsibility to perform such work. The baseline construction schedule, or subsequent schedule updates, does not modify the contract documents.

a.

D.

Baseline Schedule Requirements 1. Define a complete and logical plan that can realistically be accomplished for executing the work defined in the contract. 2. Designate the baseline schedule Data Date as the day before the Notice to Proceed. Data Dates for Schedule Updates will be the day after the estimate period closes. 3. Include a well-defined work breakdown structure (WBS). Assign the WBS structure consistently and uniformly among all similar activity types. Each activity must be assigned to a WBS. 4. Include activity coding structures that allows project activities to be sorted by type of work, location of work, or as mutually agreed to by the Contractor and the Engineer. a. Use Activity Global Codes in Primavera P6. Begin each Global Code name with the UDOT Project Identification Number followed by a dash. 5. Clearly define calendars. a. Begin each calendar name with the UDOT Project Identification Number followed by a dash. b. Include UDOT holidays as non-work days. c. Identify and include potential non-work weather days in calendar months. Assumptions for non-work weather days should be based on 15-year averages from NOAA data for the closest weather station, or other applicable sources as approved by the Engineer. Describe sources and calculations used for assumptions in the baseline narrative. d. Include calendars that adequately represent non-work days associated with limitations (such as paving, utilities, landscape, etc.). e. Include a 7-day calendar to be utilized for cure, settlement, and other activities as appropriate. f. Assign calendars consistently among similar activity types.

6.

7.

8.

9.

10.

11.

Provide a sufficient number of activities to assure adequate planning and to allow monitoring and evaluation of progress and payments. a. Define activities to a level of detail acceptable to the Engineer. b. A baseline schedule with less than 500 activities or more than 2000 activities requires justification by the Contractor and approval by the Engineer. c. Include additional activities as required by the Engineer. Include milestones to define significant contractual events such as Notice to Proceed, Substantial Completion, completion of major segments of work, major traffic changes, and coordination points with outside entities (such as utilities, special service districts, etc.). Include activities that define significant interaction points with the Department and other entities such as subcontractors, vendors and suppliers, utilities, local governments, and special service districts. Describe activities so that the scope of work is identifiable and progress on each activity can be measured. a. Provide a unique and legible activity description to easily identify the specific activity. Indicate in each activity description its associated scope and location of work (such as type of work, bridge number, station to station locations, side of highway, pipe number, etc.). Also include a verb in the activity description to indicate the action undertaken (such as install, place, fabricate, etc.). There should be no duplicate activity descriptions. Define the duration of each activity. a. Limit the maximum duration of any activity to 20 days unless otherwise accepted by the Engineer. Exceptions could include non-work type activities such as mobilization, design, fabrication, settlement durations, curing, and long lead procurement items. b. Use of level of effort (LOE) activities requires Engineer approval. c. Duration for each activity should be the time required to complete the Work based on the quantity of work divided by reasonably anticipated production rate(s). d. Include separate activities for cure time, major inspection points requiring preparation, submittal periods, and other time consuming activities. Clearly identify the relationships and logic that tie activities together. a. Each activity is to have at least one predecessor and one successor activity, except for Notice to Proceed and Substantial Completion milestones.

12. 13. 14. 15.

16.

17.

Avoid unnecessary relationships or excessive ties to end milestones. c. Provide a list of activities utilizing lags and the justification for the use of each lag. Do not utilize any negative lags. Do not have any constrained activities unless accepted by the Engineer. Do not sequester project total float through manipulating calendars, extending activities durations, or any other such methodology. Use of negative float is not acceptable in the baseline construction schedule. Clearly show the critical path. a. Use the longest path schedule option setting to define critical activities. b. Use the retained logic schedule option setting to calculate the critical path and controlling activities in the baseline schedule and subsequent schedule updates. c. Do not use the leveling resources schedule option without prior notification and concurrence of schedule update procedures with the Engineer. d. Ensure the schedule has been progressed (by using the Schedule function under Tools in Primavera) prior to submission with no further modifications made to the schedule following progression. The Schedule function allows the software to complete a forward and backward pass of the data to calculate float and longest path. As a guideline, near-critical activities should be limited to 15% of the construction activities not including LOE, etc. Near-critical is defined as activities with total float of 15 days or less. a. If more than 15% of the activities in the baseline schedule are near-critical, then the Contractor is to provide justification for acceptance by the Engineer. b. If more than 15% of the activities in a schedule update become near-critical, then the Contractor is to present a recovery plan if requested by the Engineer. Resource-load the baseline schedule. a. Provide a list of crews with associated labor and equipment resources to the Engineer with the baseline schedule submittal. b. Define crews in Primavera as a Labor Resource Type and assign to appropriate activities. c. Optional: Define equipment as Non-Labor Resource Type for each type and size of equipment and assign to appropriate activities. Or, it is acceptable to define crews with associated labor and equipment and provide to the Engineer as described above.

b.

18.

19. 20. 21. 22.

Do not include any costs for Labor resources (price/unit = $0.00). e. If composition of crews (labor or equipment) changes at any time during the course of the Project, revise the Schedule Updates to reflect the changes and provide the Engineer with a revised list of crews with associated labor and equipment resources. f. No request or claim for contract time extension or additional costs based on labor or equipment resource shortages will be considered unless the baseline and subsequent schedule updates are accurately resource-loaded. Cost-load the baseline schedule. a. Provide sufficient number of activities so that budget of any one activity does not exceed $200,000.00, unless otherwise approved by the Engineer. b. Create Resource IDs and Resource Names in Primavera that are based on UDOT bid items. c. Begin each Resource ID with the UDOT Project Identification Number followed by a dash. d. Define costs as Material Resource Type. e. Each resource (bid item) should be allocated and assigned to activities in the appropriate quantity to accomplish the Work within the activity duration. f. Modifications to the project budget during the course of the Project will also need to be revised in Schedule Updates. 1) Change Orders as approved by the Department are to be added into the schedule with appropriate activities, resources, and units/budget to represent the modified scope of work. Throughout the Project, total budget in the schedule should match revised Contract Amount inclusive of all authorized Change Orders. 2) When the Contractor adds or splits out activities in the course of revising a Schedule Update, units/budget and resources for those activities must also be reallocated to represent appropriate quantity to accomplish the Work within the activity duration. Payments are based on estimates prepared by the Engineer in accordance with Section 01282. Actual units/costs incurred through the course of the Project will be tracked in PDBS. Set the activity percent complete to Physical for all activities other than LOE activities. The Department utilizes TILOS linear scheduling software to display the CPM schedule in a time-location diagram. The Contractor ensures that activity coding and stationing in the

d.

baseline schedule and subsequent schedule updates is accurate and up-to-date to accommodate the use of the software. a. Include a user-defined field for stationing start. Start stationing should be at the location where work is intended to begin. b. Include a user-defined field for stationing end. End stationing should be at the location where work is intended to end. c. Stationing should be entered in such a way as to communicate the direction of the work. d. All stationing must be associated with the mainline for data to plot correctly on a linear display. If there are activities that cross the mainline (such as cross-streets or utilities) provide stationing consistent with the mainline. Do not use any alternative stationing that may be provided on design or utility plans unless approved by the Engineer in advance. If an activity is not located on the mainline or does not cross the mainline, then stationing may not need to be provided for that activity upon concurrence with the Engineer. e. Create and assign to each activity a Global Code for work elements to indicate the type of work related to an activity. Begin the Global Code name with the UDOT Project Identification Number followed by a dash. f. Establish code values as agreed upon with the Engineer in the Baseline Schedule Pre-Submittal Meeting. A guideline for code values is provided in the following table. Work Element Code Values
Code Value
AGGREGATE CLEAR&GRUB DEMO DRAINAGE EXCAVATION FLATWORK LANDSCAPE MOT PAVING PROCURE ROW SIGNALS SIGNING STRIPING STRUCTURES SUBSTRUCTURE

Description
Granular, UTBC, Finish Clear & Grub, Removal Building demolition, other Pipe Cut, fill, excavate Curb, gutter, sidewalks Topsoil, mulch, seeding Maintenance of Traffic PCCP, HMA, OGSC Procurement of materials Right-of-Way Signals, foundations, poles Signing - Permanent Striping - Permanent Box culvert, headwall (non-bridge) Foundation, Columns, Bent, Piles,

SUPERSTRUCTURE SURCHARGE TRAIL UTILITY-COMM UTILITY-GAS UTILITY-POWER UTILITY-WATER WALLS NA

Abutments (bridge) Girders, Deck, Approach Slabs, Parapet, Polymer Overlay (bridge) Consolidation & Settlement Times Trails - Pedestrian & Bike Utility Communication Utility Gas Utility Power Utility Water/Irrigation/Sewer Noise, MSE, Retaining Not Applicable Not on Mainline, Misc, LOE, etc.

E.

Accelerated Baseline Schedule 1. If the Contractor wishes to propose an accelerated schedule for early completion, the Contractor must request in writing that the Department identify additional Department costs required to support the accelerated schedule such as increased staff for inspection, testing, and overtime. a. The Contractor is responsible for paying for these added costs unless waived by the Department on the basis of other benefits accrued to the Department. b. The acceptance of an early completion schedule is at the sole discretion of the Department. Baseline Schedule Narrative Requirements 1. Describe the construction philosophy supporting the approach to the work outlined in the baseline schedule. 2. Describe the approach used to apply relationships between activities, such as: physical or chronological relationships between work activities; sequencing due to crew or equipment resources; or, timing of work based on limitations (such as ROW, environmental, utilities, etc.). 3. Describe any limited resources, potential conflicts, or other salient items that may affect the schedule and how they may be resolved. 4. Describe the critical path and identify challenges that may arise associated with the critical path. 5. Describe how coordination will be handled with entities such as subcontractors, vendors and suppliers, utilities, local governments, and special service districts. 6. Describe activity coding structures and how they will be used. 7. Provide a list of resources describing crews, crew size, major equipment, and production rates. 8. Provide list of applicable activities and justification for usage of: a. Activities with durations exceeding 20 days. b. Constraints.

F.

9.

Unusual calendars. Assumptions and calculations for non-work weather days added to calendars. d. Lag. e. Near-critical activities, if more than 15% of the activities in the baseline schedule are near-critical. Along with the baseline narrative, include layouts generated from Primavera (PDF file) to illustrate the following: a. Layout to demonstrate Contractors approach to work (based on WBS or other applicable coding). At a minimum include columns for activity id, activity name, start, finish, original duration, remaining duration, total float, longest path, budgeted cost, and Gantt chart. b. Longest Path layout. c. Other layouts or reports as agreed upon with the Engineer.

c.

ANTICIPATED MONTHLY PAYMENT SCHEDULE A. The Anticipated Monthly Payment Schedule must be submitted and approved with the baseline schedule. 1. Use estimate period closing dates to generate the payment schedule. 2. Prepare the payment schedule using data or reports generated from the Primavera baseline construction schedule. Submit a revised Anticipated Monthly Payment Schedule with the corresponding Schedule Update under the following conditions: 1. Changes to Contract start or completion dates, changes to significant milestone dates, or Contract suspension. 2. Change orders are approved increasing or reducing the contract amount sufficient to vary actual payments more than 10 percent from the previously accepted schedule. 3. As requested by the Engineer. 4. The revised Anticipated Monthly Payment Schedule is subject to Engineers approval.

B.

CONSTRUCTION SCHEDULE UPDATES A. Monthly Progress Meetings 1. Conduct monthly progress meetings to review and discuss the status of the project. Discuss critical path, changes in sequencing or approach to work, change orders, and potential delay. Current and potential issues should be addressed with the intent of finding the most effective solutions to problems.

2. 3.

Attendees to include, at a minimum, the Contractors project manager, Contractors qualified scheduler, and Engineer. Record an action item list that specifies who is responsible for resolving existing or pending issues and the date by which the issue must be resolved to avoid contract delays.

B.

Submission of Schedule Updates 1. Submit an updated schedule each month during the life of the contract until the closing date for the scheduled progress payment following project final acceptance. 2. The Schedule Update is due within 5 working days from the close of the estimate period. 3. The Engineer reviews the schedule and returns it as either accepted, accepted with comments, or returned with comments for resubmission within 5 working days from the date of receipt. a. The Contractor is to address comments and revise the schedule as necessary to the satisfaction of the Engineer. 4. An acceptable schedule must be received within 10 working days from the close of estimate period to be eligible for incentive, if applicable. a. Schedule Updates returned for resubmission by the Engineer must be revised and resubmitted by the Contractor within the same 10 working days timeframe and ultimately result in acceptance by the Engineer in order to be eligible for incentive, if applicable. 5. Submit to the Engineer a Schedule Update with schedule narrative and accompanying layouts or reports, to include: a. One electronic copy of Primavera software file (.XER file). b. Two hard copies and one electronic copy of narrative report. c. Two hard copies and one electronic (PDF file) copy of layouts as generated from Primavera, as outlined in the Schedule Update Narrative Requirements in this section. 6. The Engineer does not approve a progress payment until an acceptable schedule update has been received, reviewed, and accepted. a. The Engineer has 5 working days to review the schedule update and return it as either accepted, accepted with comments, or returned with comments for resubmission. Upon acceptance of the schedule update the Engineer has an additional 5 working days to complete review of the progress payment. b. If a schedule update is returned by the Engineer with comments for resubmission, then it is the responsibility of the Contractor to promptly revise and resubmit the schedule update. Upon receipt of the revised schedule update, the Engineer has 5 working days to review the revised schedule

7.

8.

and return it as either accepted, accepted with comments, or returned with comments for resubmission. Upon acceptance of the revised schedule update the Engineer has an additional 5 working days to complete review of the progress payment. Failure to include any element of work required by the contract in the accepted baseline construction schedule or subsequent schedule updates does not relieve the Contractors responsibility to perform such work. The baseline construction schedule, or subsequent schedule updates, does not modify the contract documents.

C.

Schedule Update Requirements 1. Comply with all baseline schedule requirements. 2. Designate the Data Date as one day after the estimate period closing date for the monthly Schedule Update and progress payment. 3. Show actual progress for each activity: a. Actual start and finish dates for completed activities. b. Actual start dates, physical percent complete, and remaining duration for activities in progress. c. Projected sequences of activities for future work. d. Revised relationships and durations for unfinished activities, if warranted. e. A well-defined critical path. 4. Ensure the Schedule Update accurately reflects as-built information for each activity shown on previous schedules. 5. Ensure planned budget and resources (bid items) in Schedule Updates match Contract Amount or revised Contract Amount inclusive of all authorized Change Orders. 6. Ensure physical percent complete for each activity is kept up-to-date. Physical percent complete in Schedule Updates should correlate with percent complete of bid items as paid through PDBS. 7. Accurately represent all planning changes, adjustments, or revisions in sequencing and timing of remaining work. 8. If work is performed out of sequence, the Contractor is required to implement logic changes consistent with the retained logic method of scheduling to allow the out-of-sequence work to proceed. 9. Through submittal of the Schedule Update, the Contractor may demonstrate proposed modifications to planned work that require adding or deleting activities, changing activity descriptions, or revising activity durations or logic. Provide the reason or justification for the changes, and describe any resulting affects or impacts on the project schedule in the update narrative. The Engineer reviews the justification for proposed changes and either

10.

accepts or rejects the proposed modifications as part of the Schedule Update review. a. Make every effort to minimize the number of changes. b. No changes are to disrupt the integrity or comparative relationship between current and previous accepted baseline schedules or schedule updates. c. An activity ID must only be used once (i.e., do not delete an activity then create a new activity at a later date utilizing the same activity ID). d. Activity descriptions may be revised for clarification, but are not to be altered to represent a different scope than originally intended. e. Changes to critical/near-critical paths should be carefully analyzed as to cause of the change and to ensure such changes were intended by the Contractor as part of revisions to planned work. f. If any changes impact the Critical Path, or result in extension of the Substantial Completion date as compared to the previously accepted Schedule Update, then the Contractor is required to submit a time impact analysis as described in Article 1.19 of this Section. Ensure the schedule has been progressed (by using the Schedule function under Tools in Primavera) prior to submission with no further modifications made to the schedule following progression. The Schedule function allows the software to complete a forward and backward pass of the data to calculate float and longest path.

D.

Schedule Update Narrative Requirements 1. Describe the work performed during the estimate period. 2. Explain deviations between the work planned and the work performed for the period. 3. Describe the work to be accomplished during the next period. 4. Describe the current critical path of the project, explaining any changes since the previous update critical path. 5. Explain all changes to the schedule since the previous update. Provide the reason or justification for the changes, and describe any resulting affects or impacts to the project schedule. Particular focus should be on any changes that affect critical or near-critical paths. Explain: a. Added or deleted activities. b. Changes to activity durations. c. Revisions to actual start/finish dates as accepted in previous updates. d. Relationship or logic revisions that result in significant increases or decreases in activity float or changes to float for groups of related activities.

6.

7.

8.

e. Calendar changes. f. Addition or deletion of constraints. g. Changes to lags and justification for use of lag. h. Changes to activity unit/budget allocations. i. Changes to resource allocations. j. Changes to Critical Path. Provide status on pending items applicable to the schedule. a. Permits, easements, agreements. b. Contract changes or time adjustments. c. Time Impact Analysis. Describe current and anticipated problems or delays: a. Cause of the problem or delay. b. Impact or potential impact to planned work, milestones, or completion dates. c. Corrective action taken to date. d. Contractors plan to mitigate or resolve problem. e. Identify action the Department needs to take and timeline for actions to be taken to avoid or mitigate the problem. f. Discussion of problems or delay in the Schedule Update narrative does not relieve the Contractor of complying with contractual requirements regarding notification and documentation of claims. Along with the schedule update narrative, include layouts generated from Primavera (PDF file) to illustrate the following: a. Layout to demonstrate Contractors approach and progress of work based on WBS or other applicable coding. At a minimum include columns for activity id, activity name, start, finish, original duration, remaining duration, total float, longest path, budgeted cost, and Gantt chart. b. Longest Path layout. c. Other layouts or reports as agreed upon with the Engineer.

TIME IMPACT ANALYSIS A. A Time Impact Analysis (TIA) is a schedule or schedule fragnet and a narrative report developed specifically to demonstrate what affect a proposed change or delay has on the current scheduled completion date. The TIA illustrates the impacts of each change or delay on the current scheduled completion date or internal milestone, as applicable. Submit a TIA to the Engineer under the following circumstances: 1. If any changes in a Schedule Update impact the Critical Path, or result in extension of the Substantial Completion date as compared to the previously accepted Schedule Update.

B.

2.

3.

If the Contractor has claim for delay. Submit a separate TIA for each delay event resulting in a request for adjustment of Contract Time. a. Submission of a TIA does not relieve the Contractor of complying with all contractual requirements regarding notification and documentation of potential change orders and change orders. The Department may request at any time a TIA demonstrating impact or potential impact to the project schedule resulting from claimed delays or Change Orders which are being negotiated between the Department and the Contractor. a. Submit a TIA within 10 working days of receiving a request by the Engineer for a TIA.

C.

Time extensions will only be considered if: 1. The delay event is demonstrated to affect the controlling operation on the Critical Path. Changes that do not affect the Critical Path will not be considered as the basis for a time adjustment. 2. The total float is absorbed and the scheduled completion date is delayed one or more working days because of the change or impact. A TIA consists of the following steps or elements: 1. Establish the status of the Project before the impact by using the most recent accepted Schedule Update that has the closest data date prior to the event for TIA. 2. Identify the impact event, estimate duration of the impact, determine appropriate logic, and insert the impact activity into the schedule. Progress the schedule. 3. Demonstrate any resulting affects from the impact through layouts generated from Primavera. Filter activities to show added or modified activities and activities impacted from changes. Note any other changes made to the schedule including modifications to the calendars or constraints. TIA Submittal 1. Provide a narrative report. a. Identify the Schedule Update(s) used for analysis. b. Describe procedures used to analyze schedule impacts, including: 1) Additions, deletions, or modification to activities. 2) Modifications to the calendars or constraints. 3) Modifications to relationships. c. Describe impact or potential impact by comparing Work prior to the impact, and Work affected or predicted to be affected after the impact.

D.

E.

2.

3.

d. Describe mitigation efforts taken to date. e. Describe potential resolutions to mitigate or avoid impact. Provide schedule layouts (PDF file) as generated from Primavera. Filter activities to clearly show impacted activities and affects to Critical Path. Multiple layouts may be required to adequately demonstrate impact to Critical Path. At a minimum, provide a layout demonstrating associated activities prior to impact, and a layout demonstrating associated activities after impact is inserted and the schedule is progressed. Include other information or documentation pertinent to the analysis.

F.

Incorporation of TIA activities into the current Schedule Update submittal requires approval of the Engineer.