Primavera P6 Technical Guidlines

P6 TECHNICAL GUIDELINES

P6 TECHNICAL GUIDELINES v1.1.docx of 5 7/19/2009 12:13 PM

Version 1.1As of July 19, 2009

The intent of this document is to provide additional technical guidelines for CM/CS and Construction Contractors forthe development of the Project Schedules. This document does not supersede the Contract, the CM/CS guidancedocument or any amendments to the Contract by The Owner.

A. Scheduling Software: Primavera (P6) version 6.2 or newer release.

B. Language: Language used shall be English.

C. Currency: Currency shall be Libyan Dinar (LYD). Follow the guidelines below when creating the currency in P6:

No. of Decimal places: 2Decimal Symbol: Period (.)Digit Grouping Symbol: Comma (,)

D. Project ID: Contractors shall use the approved format developing the Project ID for the schedule. This Format willbe provided by the Program Manager.

E. Reporting Frequency: Monthly

F. WBS: Contractors shall use the approved WBS in developing the Project schedule. All activities shall be codedunder their respective WBS elements.

G. Planning Unit: Day

H. Critical Path Method: Longest Path

I. Hours per Time Period settings shall be:

J. Activity ID: Include a unique identification number for each activity. Activity ID numbers shall not be changed, orreassigned. Activity ID logic shall at least include the numbers from levels 1 thru 3 of the approved WBS.

K. Activity descriptions: Clearly and uniquely define each activity name with a description of the work that is readilyidentifiable to inspection staff and the progress of each activity can be measured. Each Activity shall have anarrative description consisting at a minimum of a verb or work function (i.e., form, pour, excavate, etc), an object(i.e., slab, footing, wall, etc), and a location (i.e., Mile marker, Zone, street, etc). The work related to each Activityshall be limited to one Area or Location of the contract, and one Responsible Party of the contract.

Day Week Month Year8 40 172 2000



L. Activity durations: With the exception of Submittal/Procurement activities, activity durations shall not exceed 20days unless specifically authorized by the owner.

M. Activity Relationships: Assign predecessors and successors relationships to each activity. No open ended activitieswill be accepted, with the exception of the first activity and last activity in the schedule.

N. Project Activity Codes:1. Only Project Activity Codes shall be used. The use of Global Activity codes is not permitted, except

those established by the owner.2. The owner may direct the contractor to create certain Project Activity Codes as needed to facilitate

review of the Project Schedule.3. The Project Activity Code names shall include the Project number and the description of the Activity

Code (i.e. x.xx.xxxx – code description)

O. Project Calendars:1. Only Project Calendars shall be used. The use of Global Calendars is not permitted, except those

established by the owner.2. The Calendar names shall include the Project number and the description of the Calendar (i.e.

x.xx.xxxx – 5-day Work week w/holidays)3. Standard work hours per day for calendar shall be 8hrs/day. Create separate calendars for night work

if required. Work hours for day time calendar shall be 08:00hrs to 17:00hrs. Work hours for nightcalendars shall be 20:00hrs to 05:00hrs next day.

4. The Contractor shall incorporate any seasonal restrictions within calendars assigned to activities.5. Calendar shall include all Libyan National and Religious Holidays at a minimum. These Holidays are:

DATE* EVENTMarch 2 Jamahiriya DayMarch 9 Prophet’s Birthday

September 1 National Day*September 21, 22, 23 Eid al-Fitr

*November 29 , 30 Eid al-Adha*The dates for Religious Holidays are based on the Muslim Calendar and are subject tochange based on government approval and announcement.

P. Milestones:1. Create milestone activities for significant contractual events including, but not limited to the following:

I. Contract Award VII. MobilizationII. Notice to Proceed, VIII. OutsideAgency Coordination

III. HIB Approvals IX. Phasing and/or StagingIV. ROW Availability X. Interim Contractual MilestonesV. Long Lead Procurement Items XI. Substantial Completion,

VI. Camp Setup XII. Contract Completion

2. All milestone activities in the schedule shall be assigned a project calendar that reflects work beingallowed 365 days a year and 24 hours per day.



Q. Constraints: The use of constraints is permitted only by written approval from HIB/AECOM Program Manager.

R. Lags: The use of lags is permitted only by written approval from HIB/AECOM Program Manager.

S. Cost and Resources: The schedule shall be Resource and Cost loaded

T. Activity Resources: Resource loading is required. Labor, equipment and material resources shall be assigned toeach activity in the schedule. Resource ID shall include the Project number and the description of the resource(i.e. x.xx.xxxx – Concrete Worker).

U. Resource Calendars: Any calendars related to specific resources (i.e., a specific person or piece of equipment) shallbe established as Resource Calendars, with the Calendar name clearly identifying the resource. Resource CalendarID shall include the Project number and the description of the resource calendar (i.e. x.xx.xxxx – Carpenters 5-day).

V. Narrative: Include a narrative in Microsoft Word and/or Adobe Acrobat format that includes the followinginformation:

1. General Project Information :i. Contractor Nameii. Project Numberiii. HIB Numberiv. Project Descriptionv. Project Type (Infrastructure or Housing)vi. Regionvii. Shabiaviii. Schedule (i.e. Baseline Schedule, Schedule Update no.1)ix. Schedule filenamex. Schedule data date

2. Project Metrics:

Schedule data Cost dataContract Start Date Contract AmountContract Finish Date Approved Modifications

Contract Duration Current Contract AmountPercent Complete Payments

Projected Finish Date Remaining Contract AmountOverall Total Float

3. General Scope of the Work.4. Contractor’s approach to how the work will be sequenced and executed.5. Contractual Milestones (If any).6. Describe Project Progress during this reporting period. Include progress on Major Work Elements.7. Provide a description of the Project’s Critical Path. Describe any changes to the critical path since the

last Monthly Progress Schedule submission and the impacts of such changes. Describe any challengesthat may affect the Critical Path.

8. 30-Day Look Ahead for Major Work Elements.



9. List any problems encountered or potential problems that are anticipated going forward and theproposed solutions to such problems.

10. Schedule/Logic Changes:

i. List Added/Deleted Activitiesii. List all changes in relationships between activities, and the reason(s) for and the

impact(s) of such changes.iii. List all Original Duration Changes (subject to approval by HIB/AECOM)iv. Justification for activity durations exceeding the designated limit (subject to approval

by HIB/AECOM)v. List of proposed constraints in the schedule with Justification (subject to approval by

HIB/AECOM)vi. List of proposed activity lags in the schedule with Justification (subject to approval by

HIB/AECOM)

W. Required Graphs/Lists:1. Earned Value Graph. A P6 Line Graph showing Budgeted, Earned Value and Actual Costs (including

Estimate to Completion) for the entire duration of the Project.2. Cashflow Graph. A bar Graph Showing actual and Projected Cashflow for the entire duration of the

Project3. List of calendars. List all changes to the project calendars, and the reason(s) for and the impact(s) of

such changes.4. List of Activity Codes5. List of Resources. This List shall include all changes made to the Resource dictionary including, but

not limited to, added and deleted resources and changes to existing resources (i.e., unit, price/unit,quantity)

X. Deliverables:1. The data date for the monthly schedule updates shall be the first of the month. Within 5 working

dates of the data date, the contractor shall submit the schedule, its narrative and the required reportsto the CM/CS for review. Within 5 working days of receipt of the schedule The CM/CS will review,approve and forward the contractor’s schedules along with the CM/CS Reports as shown in the CM/CSGuidance Document to the designated HIB/AECOM representative.

2. The submission of the schedule and the narrative shall be in electronic format (.XER for P6 and .PDFfor narrative and barchart) and can initially be made via e-mail. The contractor shall also submit a CDcontaining electronic copies of all required submittals and three color hardcopies of a barchartSchedule on A3 (297 X 420mm) paper size. The barchart schedule shall include all activities grouped byWBS. Sort activities by Early Start Date in ascending order. Adjust the timescale on the barchartportion to show the complete duration of the Project. The critical path activities shall be shown in redcolor. Use different colors for non-critical activity bars. The activity relationship lines shall be visible.The barchart schedule shall include, but not limited to, the following columns:

i. Activity IDii. Activity Descriptioniii. Percent Completeiv. Original Durationv. Remaining Durationvi. Total Floatvii. Start



viii. Finish

3. The AECOM PM may from time to time direct the CM and/or the contractor to submit additionalreports as required to facilitate proper review and approval of the schedule.

Primavera P6 Technical Guidlines

Documents

Transcript of Primavera P6 Technical Guidlines