7/27/2019 uconowner

1/16

Project Controls Specification Summary

The following includes some information about the anticipated project controlrequirements of the construction contractor and the duties of the Consultant acting onUDOTs 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 becomefamiliar.

DEFINITIONS

Critical Path: The series of activities that determine the projects substantialcompletion date; a delay to any of these activities could delay the finish date of theentire 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 theentire project which focuses on the Critical Path activities that affect the completion ofthe project.

Time Impact Analysis (TIA): A schedule or schedule fragnet, and narrative reportdeveloped specifically to demonstrate what affect a proposed change or delay has onthe current scheduled project substantial completion date.

Total Float: The difference between the earliest and latest allowable start or finishtimes for an activity which generally represents the amount of time an activity can bedelayed without delaying the project substantial completion date.

Work Breakdown Structure (WBS): A hierarchy of work that must be accomplished tocomplete the project. It is structured in levels of work detail that describe the projectand identifiable work elements.

PROGRESS PAYMENTS

Prior to payment, the Engineer requires documentation according to UDOTSpecifications to substantiate acceptance of materials and work items for both qualityand quantity.

As approved by the Engineer, payment for work performed on a unit or measured basismay be released up to 90 percent of the value of the quantity associated with theschedule activity while documentation is in the process of being received andsubstantiated by the Engineer. The remaining 10 percent of the value will be paid whenthe work is complete AND all required documentation is received and substantiated bythe Engineer.

7/27/2019 uconowner

2/16

The Engineer cannot approve payment prior to receiving documentation when suchdocumentation is required by contract prior to placement of materials (i.e., materialcertifications, FHWA requirement, Buy America, etc.).As approved by the Engineer, partial payment for work performed on a lump sum orplan quantity activity may be released as follows:

a. Payment may be released at 50 percent of the activity value when thephysical progress of an activity is at least 50 percent achieved andaccepted according to Contract requirements.

b. Payment may be released at 90 percent of the activity value when thephysical progress of an activity is 100 percent achieved and acceptedaccording to Contract requirements, and documentation is in the processof being received and substantiated by the Engineer. The remaining 10percent of the value will be paid when the work is complete AND allrequired 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 ormanipulated for payment purposes. All schedule activities are to be updated accordingto progress in the field and reflect accurate as-built information in accordance withcontract requirements. See Section 00555S.

QUALIFIED SCHEDULER

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

BASELINE CONSTRUCTION SCHEDULE

A. Baseline Schedule Pre-Submittal Meeting1. Conduct a pre-submittal schedule meeting to:

a. Review the requirements of this section prior to submittal ofthe baseline construction schedule.

b. Determine estimate period closing dates upon which themonthly schedule updates and progress payments will begenerated (with approval of the Engineer).

2. Attendees to include, at a minimum, the Contractors projectmanager, Contractors qualified scheduler, and the Engineer.

7/27/2019 uconowner

3/16

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

B. General Requirements1. Provide the Engineer with a baseline construction schedule

meeting the requirements of this section using Primavera 6.0 orcurrent version or Primavera Contractor. Provide a schedulenarrative 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, vendorsand suppliers, utilities, local governments, special service districts,and the Department.

4. Employ a sufficient workforce, supply adequate materials andequipment, and progress the work with such diligence as tomaintain the rate indicated in the accepted baseline construction

schedule.5. All costs to maintain the schedule are solely the Contractorsobligation and at no expense to the Department.

C. Baseline Schedule Submission1. Establish a sequential numbering system for schedule submittals

and associated reports to allow easy identification of BaselineSchedule(s), Schedule Updates, and Schedule Updateresubmissions,as acceptable to the Engineer.

2. Submit to the Engineer a baseline construction schedule withschedule narrative within 7 calendar days of the Notice to Proceedin 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 theBaseline Schedule Narrative Requirements in this section.

3. The Engineer reviews the baseline schedule and returns it asaccepted, accepted with comments, or returned with comments forresubmission 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 within30 calendar days from Notice to Proceed.

5. No progress payments are made before the Engineer accepts thefinal baseline schedule.

6. The Contractor is solely responsible for planning and executing thework. Engineers acceptance of the baseline schedule does not:

7/27/2019 uconowner

4/16

a. Imply approval of any construction methods or relieve theContractors responsibility to provide sufficient materials,equipment, and labor to guarantee completion of the projectin accordance with the Contract.

b. Attest to the validity of assumptions, activities, relationships,

sequences, resource allocations, or any other aspect of thebaseline construction schedule.7. Failure to include any element of work required by the contract in

the accepted baseline construction schedule does not relieve theContractors responsibility to perform such work.

8. The baseline construction schedule, or subsequent scheduleupdates, does not modify the contract documents.

D. Baseline Schedule Requirements1. 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 theNotice to Proceed. Data Dates for Schedule Updates will be theday after the estimate period closes.

3. Include a well-defined work breakdown structure (WBS). Assignthe WBS structure consistently and uniformly among all similaractivity types. Each activity must be assigned to a WBS.

4. Include activity coding structures that allows project activities to besorted by type of work, location of work, or as mutually agreed to bythe Contractor and the Engineer.a. Use Activity Global Codes in Primavera P6. Begin each

Global Code name with the UDOT Project IdentificationNumber 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 daysshould be based on 15-year averages from NOAA data forthe closest weather station, or other applicable sources asapproved by the Engineer. Describe sources andcalculations used for assumptions in the baseline narrative.

d. Include calendars that adequately represent non-work daysassociated 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.

7/27/2019 uconowner

5/16

6. Provide a sufficient number of activities to assure adequateplanning and to allow monitoring and evaluation of progress andpayments.a. Define activities to a level of detail acceptable to the

Engineer.

b. A baseline schedule with less than 500 activities or morethan 2000 activities requires justification by the Contractorand approval by the Engineer.

c. Include additional activities as required by the Engineer.7. Include milestones to define significant contractual events such as

Notice to Proceed, Substantial Completion, completion of majorsegments of work, major traffic changes, and coordination pointswith outside entities (such as utilities, special service districts, etc.).

8. Include activities that define significant interaction points with theDepartment and other entities such as subcontractors, vendors andsuppliers, utilities, local governments, and special service districts.

9. Describe activities so that the scope of work is identifiable andprogress on each activity can be measured.a. Provide a unique and legible activity description to easily

identify the specific activity. Indicate in each activitydescription its associated scope and location of work (suchas type of work, bridge number, station to station locations,side of highway, pipe number, etc.). Also include a verb inthe activity description to indicate the action undertaken(such as install, place, fabricate, etc.). There should be noduplicate activity descriptions.

10. Define the duration of each activity.a. Limit the maximum duration of any activity to 20 days unless

otherwise accepted by the Engineer. Exceptions couldinclude non-work type activities such as mobilization, design,fabrication, settlement durations, curing, and long leadprocurement items.

b. Use of level of effort (LOE) activities requires Engineerapproval.

c. Duration for each activity should be the time required tocomplete the Work based on the quantity of work divided byreasonably anticipated production rate(s).

d. Include separate activities for cure time, major inspectionpoints requiring preparation, submittal periods, and othertime consuming activities.

11. Clearly identify the relationships and logic that tie activitiestogether.a. Each activity is to have at least one predecessor and one

successor activity, except for Notice to Proceed andSubstantial Completion milestones.

7/27/2019 uconowner

6/16

b. Avoid unnecessary relationships or excessive ties to endmilestones.

c. Provide a list of activities utilizing lags and the justification forthe use of each lag. Do not utilize any negative lags.

12. Do not have any constrained activities unless accepted by the

Engineer.13. Do not sequester project total float through manipulating calendars,extending activities durations, or any other such methodology.

14. Use of negative float is not acceptable in the baseline constructionschedule.

15. 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 baselineschedule and subsequent schedule updates.

c. Do not use the leveling resources schedule option withoutprior notification and concurrence of schedule updateprocedures with the Engineer.

d. Ensure the schedule has been progressed (by using theSchedule function under Tools in Primavera) prior tosubmission with no further modifications made to theschedule following progression. The Schedule functionallows the software to complete a forward and backwardpass of the data to calculate float and longest path.

16. As a guideline, near-critical activities should be limited to 15% ofthe construction activities not including LOE, etc. Near-critical isdefined 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 justificationfor acceptance by the Engineer.

b. If more than 15% of the activities in a schedule updatebecome near-critical, then the Contractor is to present arecovery plan if requested by the Engineer.

17. Resource-load the baseline schedule.a. Provide a list of crews with associated labor and equipment

resources to the Engineer with the baseline schedulesubmittal.

b. Define crews in Primavera as a Labor Resource Type andassign to appropriate activities.

c. Optional: Define equipment as Non-Labor Resource Typefor each type and size of equipment and assign toappropriate activities. Or, it is acceptable to define crewswith associated labor and equipment and provide to theEngineer as described above.

7/27/2019 uconowner

7/16

d. Do not include any costs for Labor resources (price/unit =$0.00).

e. If composition of crews (labor or equipment) changes at anytime during the course of the Project, revise the ScheduleUpdates to reflect the changes and provide the Engineer

with a revised list of crews with associated labor andequipment resources.f. No request or claim for contract time extension or additional

costs based on labor or equipment resource shortages willbe considered unless the baseline and subsequent scheduleupdates are accurately resource-loaded.

18. 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 otherwiseapproved 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 IdentificationNumber 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 theWork within the activity duration.

f. Modifications to the project budget during the course of theProject 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 modifiedscope of work. Throughout the Project, total budgetin the schedule should match revised ContractAmount inclusive of all authorized Change Orders.

2) When the Contractor adds or splits out activities in thecourse of revising a Schedule Update, units/budgetand resources for those activities must also bereallocated to represent appropriate quantity toaccomplish the Work within the activity duration.

19. Payments are based on estimates prepared by the Engineer inaccordance with Section 01282.

20. Actual units/costs incurred through the course of the Project will betracked in PDBS.

21. Set the activity percent complete to Physical for all activities otherthan LOE activities.

22. The Department utilizes TILOS linear scheduling software todisplay the CPM schedule in a time-location diagram. TheContractor ensures that activity coding and stationing in the

7/27/2019 uconowner

8/16

baseline schedule and subsequent schedule updates is accurateand 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 intendedto begin.

b. Include a user-defined field for stationing end. Endstationing should be at the location where work is intendedto end.

c. Stationing should be entered in such a way as tocommunicate the direction of the work.

d. All stationing must be associated with the mainline for datato plot correctly on a linear display. If there are activities thatcross the mainline (such as cross-streets or utilities) providestationing consistent with the mainline. Do not use anyalternative stationing that may be provided on design orutility plans unless approved by the Engineer in advance. If

an activity is not located on the mainline or does not crossthe mainline, then stationing may not need to be provided forthat activity upon concurrence with the Engineer.

e. Create and assign to each activity a Global Code for workelements to indicate the type of work related to an activity.Begin the Global Code name with the UDOT ProjectIdentification Number followed by a dash.

f. Establish code values as agreed upon with the Engineer inthe Baseline Schedule Pre-Submittal Meeting. A guidelinefor code values is provided in the following table.

Work Element Code Values

Code Value DescriptionAGGREGATE Granular, UTBC, Finish

CLEAR&GRUB Clear & Grub, Removal

DEMO Building demolition, other

DRAINAGE Pipe

EXCAVATION Cut, fill, excavate

FLATWORK Curb, gutter, sidewalks

LANDSCAPE Topsoil, mulch, seeding

MOT Maintenance of Traffic

PAVING PCCP, HMA, OGSC

PROCURE Procurement of materials

ROW Right-of-Way

SIGNALS Signals, foundations, poles

SIGNING Signing - Permanent

STRIP ING Striping - Permanent

STRUCTURES Box culvert, headwall (non-bridge)

SUBSTRUCTURE Foundation, Columns, Bent, Piles,

7/27/2019 uconowner

9/16

Abutments (bridge)

SUPERSTRUCTUREGirders, Deck, Approach Slabs, Parapet,Polymer Overlay (bridge)

SURCHARGE Consolidation & Settlement Times

TRAIL Trails - Pedestrian & Bike

UTILITY-COMM Utility CommunicationUTILITY-GAS Utility Gas

UTILITY-POWER Utility Power

UTILITY-WATER Utility Water/Irrigation/Sewer

WALLS Noise, MSE, Retaining

NANot Applicable Not on Mainline, Misc,LOE, etc.

E. Accelerated Baseline Schedule1. 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 tosupport the accelerated schedule such as increased staff forinspection, testing, and overtime.a. The Contractor is responsible for paying for these added

costs unless waived by the Department on the basis of otherbenefits accrued to the Department.

b. The acceptance of an early completion schedule is at thesole discretion of the Department.

F. Baseline Schedule Narrative Requirements1. Describe the construction philosophy supporting the approach to

the work outlined in the baseline schedule.2. Describe the approach used to apply relationships betweenactivities, such as: physical or chronological relationships betweenwork 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 salientitems that may affect the schedule and how they may be resolved.

4. Describe the critical path and identify challenges that may ariseassociated with the critical path.

5. Describe how coordination will be handled with entities such assubcontractors, 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.

7/27/2019 uconowner

10/16

c. Unusual calendars. Assumptions and calculations fornon-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.

9. Along with the baseline narrative, include layouts generated fromPrimavera (PDF file) to illustrate the following:a. Layout to demonstrate Contractors approach to work (based

on WBS or other applicable coding). At a minimum includecolumns for activity id, activity name, start, finish, originalduration, 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.

ANTICIPATED MONTHLY PAYMENT SCHEDULE

A. The Anticipated Monthly Payment Schedule must be submitted andapproved 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.

B. Submit a revised Anticipated Monthly Payment Schedule with thecorresponding 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 percentfrom the previously accepted schedule.

3. As requested by the Engineer.4. The revised Anticipated Monthly Payment Schedule is subject to

Engineers approval.

CONSTRUCTION SCHEDULE UPDATES

A. Monthly Progress Meetings1. Conduct monthly progress meetings to review and discuss the

status of the project. Discuss critical path, changes in sequencingor approach to work, change orders, and potential delay. Currentand potential issues should be addressed with the intent of findingthe most effective solutions to problems.

7/27/2019 uconowner

11/16

2. Attendees to include, at a minimum, the Contractors projectmanager, Contractors qualified scheduler, and Engineer.

3. Record an action item list that specifies who is responsible forresolving existing or pending issues and the date by which theissue must be resolved to avoid contract delays.

B. Submission of Schedule Updates1. Submit an updated schedule each month during the life of the

contract until the closing date for the scheduled progress paymentfollowing project final acceptance.

2. The Schedule Update is due within 5 working days from the closeof the estimate period.

3. The Engineer reviews the schedule and returns it as eitheraccepted, accepted with comments, or returned with comments forresubmission 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 daysfrom the close of estimate period to be eligible for incentive, ifapplicable.a. Schedule Updates returned for resubmission by the

Engineer must be revised and resubmitted by the Contractorwithin the same 10 working days timeframe and ultimatelyresult in acceptance by the Engineer in order to be eligiblefor incentive, if applicable.

5. Submit to the Engineer a Schedule Update with schedule narrativeand 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 theSchedule Update Narrative Requirements in this section.

6. The Engineer does not approve a progress payment until anacceptable schedule update has been received, reviewed, andaccepted.a. The Engineer has 5 working days to review the schedule

update and return it as either accepted, accepted withcomments, or returned with comments for resubmission.Upon acceptance of the schedule update the Engineer hasan additional 5 working days to complete review of theprogress payment.

b. If a schedule update is returned by the Engineer withcomments for resubmission, then it is the responsibility ofthe Contractor to promptly revise and resubmit the scheduleupdate. Upon receipt of the revised schedule update, theEngineer has 5 working days to review the revised schedule

7/27/2019 uconowner

12/16

and return it as either accepted, accepted with comments, orreturned with comments for resubmission. Upon acceptanceof the revised schedule update the Engineer has anadditional 5 working days to complete review of the progresspayment.

7. Failure to include any element of work required by the contract inthe accepted baseline construction schedule or subsequentschedule updates does not relieve the Contractors responsibility toperform such work.

8. The baseline construction schedule, or subsequent scheduleupdates, does not modify the contract documents.

C. Schedule Update Requirements1. 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-builtinformation for each activity shown on previous schedules.

5. Ensure planned budget and resources (bid items) in ScheduleUpdates match Contract Amount or revised Contract Amountinclusive of all authorized Change Orders.

6. Ensure physical percent complete for each activity is keptup-to-date. Physical percent complete in Schedule Updates shouldcorrelate with percent complete of bid items as paid through PDBS.

7. Accurately represent all planning changes, adjustments, orrevisions in sequencing and timing of remaining work.

8. If work is performed out of sequence, the Contractor is required toimplement logic changes consistent with the retained logic methodof scheduling to allow the out-of-sequence work to proceed.

9. Through submittal of the Schedule Update, the Contractor maydemonstrate proposed modifications to planned work that requireadding or deleting activities, changing activity descriptions, orrevising activity durations or logic. Provide the reason orjustification for the changes, and describe any resulting affects orimpacts on the project schedule in the update narrative. TheEngineer reviews the justification for proposed changes and either

7/27/2019 uconowner

13/16

accepts or rejects the proposed modifications as part of theSchedule 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 anactivity then create a new activity at a later date utilizing thesame activity ID).

d. Activity descriptions may be revised for clarification, but arenot to be altered to represent a different scope than originallyintended.

e. Changes to critical/near-critical paths should be carefullyanalyzed as to cause of the change and to ensure suchchanges were intended by the Contractor as part of revisionsto planned work.

f. If any changes impact the Critical Path, or result in extensionof the Substantial Completion date as compared to thepreviously accepted Schedule Update, then the Contractor isrequired to submit a time impact analysis as described inArticle 1.19 of this Section.

10. Ensure the schedule has been progressed (by using the Schedulefunction under Tools in Primavera) prior to submission with nofurther modifications made to the schedule following progression.The Schedule function allows the software to complete a forwardand backward pass of the data to calculate float and longest path.

D. Schedule Update Narrative Requirements1. 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 describeany resulting affects or impacts to the project schedule. Particularfocus should be on any changes that affect critical or near-criticalpaths. 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 forgroups of related activities.

7/27/2019 uconowner

14/16

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.6. Provide status on pending items applicable to the schedule.a. Permits, easements, agreements.b. Contract changes or time adjustments.c. Time Impact Analysis.

7. 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 foractions 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 withcontractual requirements regarding notification anddocumentation of claims.

8. Along with the schedule update narrative, include layoutsgenerated 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 aminimum 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 anarrative report developed specifically to demonstrate what affect aproposed change or delay has on the current scheduled completion date.The TIA illustrates the impacts of each change or delay on the currentscheduled completion date or internal milestone, as applicable.

B. 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 comparedto the previously accepted Schedule Update.

7/27/2019 uconowner

15/16

2. If the Contractor has claim for delay. Submit a separate TIA foreach delay event resulting in a request for adjustment of ContractTime.a. Submission of a TIA does not relieve the Contractor of

complying with all contractual requirements regarding

notification and documentation of potential change ordersand change orders.3. The Department may request at any time a TIA demonstrating

impact or potential impact to the project schedule resulting fromclaimed delays or Change Orders which are being negotiatedbetween 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 Pathwill 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 orimpact.

D. 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 datadate 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 theschedule. Progress the schedule.

3. Demonstrate any resulting affects from the impact through layoutsgenerated from Primavera. Filter activities to show added ormodified activities and activities impacted from changes. Note anyother changes made to the schedule including modifications to thecalendars or constraints.

E. TIA Submittal1. 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 priorto the impact, and Work affected or predicted to be affectedafter the impact.

7/27/2019 uconowner

16/16

d. Describe mitigation efforts taken to date.e. Describe potential resolutions to mitigate or avoid impact.

2. Provide schedule layouts (PDF file) as generated from Primavera.Filter activities to clearly show impacted activities and affects toCritical Path. Multiple layouts may be required to adequately

demonstrate impact to Critical Path. At a minimum, provide alayout demonstrating associated activities prior to impact, and alayout demonstrating associated activities after impact is insertedand the schedule is progressed.

3. Include other information or documentation pertinent to theanalysis.

F. Incorporation of TIA activities into the current Schedule Update submittalrequires approval of the Engineer.