This action might not be possible to undo. Are you sure you want to continue?
Version 1.1 As of July 19, 2009 The intent of this document is to provide additional technical guidelines for CM/CS and Construction Contractors for the development of the Project Schedules. This document does not supersede the Contract, the CM/CS guidance document 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: Decimal Symbol: Digit Grouping Symbol: 2 Period (.) Comma (,)
D. Project ID: Contractors shall use the approved format developing the Project ID for the schedule. This Format will
be provided by the Program Manager.
Reporting Frequency: Monthly WBS: Contractors shall use the approved WBS in developing the Project schedule. All activities shall be coded under their respective WBS elements.
G. Planning Unit: Day H. Critical Path Method: Longest Path I.
Hours per Time Period settings shall be:
Day 8 Week 40 Month 172 Year 2000
Activity ID: Include a unique identification number for each activity. Activity ID numbers shall not be changed, or reassigned. Activity ID logic shall at least include the numbers from levels 1 thru 3 of the approved WBS. Activity descriptions: Clearly and uniquely define each activity name with a description of the work that is readily identifiable to inspection staff and the progress of each activity can be measured. Each Activity shall have a narrative 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 Activity shall be limited to one Area or Location of the contract, and one Responsible Party of the contract.
P6 TECHNICAL GUIDELINES v1.1.docx
Page 1 of 5
7/19/2009 12:13 PM
The Calendar names shall include the Project number and the description of the Calendar (i. with the exception of the first activity and last activity in the schedule. Create separate calendars for night work if required. 4. Create milestone activities for significant contractual events including. Activity durations: With the exception of Submittal/Procurement activities. 3. The Project Activity Code names shall include the Project number and the description of the Activity Code (i. VIII.xx. Milestones: 1. 5. Project Calendars: 1. III. Mobilization OutsideAgency Coordination Phasing and/or Staging Interim Contractual Milestones Substantial Completion.e. M. The use of Global Activity codes is not permitted. but not limited to the following: I. These Holidays are: DATE* March 2 March 9 September 1 *September 21. No open ended activities will be accepted. Contract Award Notice to Proceed. Activity Relationships: Assign predecessors and successors relationships to each activity. II. Only Project Calendars shall be used. activity durations shall not exceed 20 days unless specifically authorized by the owner.xxxx – 5-day Work week w/holidays) Standard work hours per day for calendar shall be 8hrs/day. Work hours for day time calendar shall be 08:00hrs to 17:00hrs. O. All milestone activities in the schedule shall be assigned a project calendar that reflects work being allowed 365 days a year and 24 hours per day. except those established by the owner. The use of Global Calendars is not permitted.1. 2. 3.xxxx – code description) 1. V. P6 TECHNICAL GUIDELINES v1. The Contractor shall incorporate any seasonal restrictions within calendars assigned to activities. N. XI. x. HIB Approvals ROW Availability Long Lead Procurement Items Camp Setup VII. Project Activity Codes: Only Project Activity Codes shall be used. Work hours for night calendars shall be 20:00hrs to 05:00hrs next day.xx. XII. x. P.docx Page 2 of 5 7/19/2009 12:13 PM . IX. 2. 23 *November 29 .P6 TECHNICAL GUIDELINES L. Calendar shall include all Libyan National and Religious Holidays at a minimum. X. 22. 30 EVENT Jamahiriya Day Prophet’s Birthday National Day Eid al-Fitr Eid al-Adha *The dates for Religious Holidays are based on the Muslim Calendar and are subject to change based on government approval and announcement.e. Contract Completion 2. VI. except those established by the owner. The owner may direct the contractor to create certain Project Activity Codes as needed to facilitate review of the Project Schedule. IV.
x. 3. Schedule Update no. Resource ID shall include the Project number and the description of the resource (i. Schedule data date 2.e. Describe Project Progress during this reporting period. Schedule filename x. 6.e. 4. Shabia viii. P6 TECHNICAL GUIDELINES v1. Resource Calendar ID shall include the Project number and the description of the resource calendar (i.xx. Contractor Name ii. 30-Day Look Ahead for Major Work Elements.docx Page 3 of 5 7/19/2009 12:13 PM . V. Constraints: The use of constraints is permitted only by written approval from HIB/AECOM Program Manager. 8. Region vii.e. Labor. Contractor’s approach to how the work will be sequenced and executed. Project Metrics: Schedule data Contract Start Date Contract Finish Date Contract Duration Percent Complete Projected Finish Date Overall Total Float Cost data Contract Amount Approved Modifications Current Contract Amount Payments Remaining Contract Amount General Scope of the Work. T. Lags: The use of lags is permitted only by written approval from HIB/AECOM Program Manager.P6 TECHNICAL GUIDELINES Q. Provide a description of the Project’s Critical Path. HIB Number iv. Project Description v. R.1) ix. equipment and material resources shall be assigned to each activity in the schedule. Project Type (Infrastructure or Housing) vi. Schedule (i. Narrative: Include a narrative in Microsoft Word and/or Adobe Acrobat format that includes the following information: 1. x. Describe any challenges that may affect the Critical Path. Describe any changes to the critical path since the last Monthly Progress Schedule submission and the impacts of such changes.xxxx – Carpenters 5-day).1. Project Number iii. Resource Calendars: Any calendars related to specific resources (i. with the Calendar name clearly identifying the resource.xxxx – Concrete Worker). Contractual Milestones (If any). U. General Project Information : i. Baseline Schedule. 5. S.e. Cost and Resources: The schedule shall be Resource and Cost loaded Activity Resources: Resource loading is required. a specific person or piece of equipment) shall be established as Resource Calendars.. 7.xx. Include progress on Major Work Elements.
vi. but not limited to. List all Original Duration Changes (subject to approval by HIB/AECOM) iv. iii.. 2. 3.XER for P6 and . v. and the reason(s) for and the impact(s) of such changes. List of Activity Codes List of Resources. A P6 Line Graph showing Budgeted. the contractor shall submit the schedule. List of proposed activity lags in the schedule with Justification (subject to approval by HIB/AECOM) W. Required Graphs/Lists: 1. Within 5 working days of receipt of the schedule The CM/CS will review. List all changes to the project calendars. The data date for the monthly schedule updates shall be the first of the month. List any problems encountered or potential problems that are anticipated going forward and the proposed solutions to such problems. Justification for activity durations exceeding the designated limit (subject to approval by HIB/AECOM) v. Schedule/Logic Changes: i. This List shall include all changes made to the Resource dictionary including. The activity relationship lines shall be visible. Cashflow Graph. Within 5 working dates of the data date. The submission of the schedule and the narrative shall be in electronic format (. Adjust the timescale on the barchart portion to show the complete duration of the Project. The barchart schedule shall include. and the reason(s) for and the impact(s) of such changes. Earned Value Graph. added and deleted resources and changes to existing resources (i. The critical path activities shall be shown in red color. but not limited to. Sort activities by Early Start Date in ascending order. vii. List Added/Deleted Activities ii. Activity ID Activity Description Percent Complete Original Duration Remaining Duration Total Float Start Page 4 of 5 7/19/2009 12:13 PM P6 TECHNICAL GUIDELINES v1. the following columns: i. its narrative and the required reports to the CM/CS for review. 5. price/unit.e. The contractor shall also submit a CD containing electronic copies of all required submittals and three color hardcopies of a barchart Schedule on A3 (297 X 420mm) paper size.docx . Earned Value and Actual Costs (including 2. iii. 10.P6 TECHNICAL GUIDELINES 9. A bar Graph Showing actual and Projected Cashflow for the entire duration of the Project List of calendars. The barchart schedule shall include all activities grouped by WBS. Deliverables: 1. iv. List all changes in relationships between activities. approve and forward the contractor’s schedules along with the CM/CS Reports as shown in the CM/CS Guidance Document to the designated HIB/AECOM representative. Estimate to Completion) for the entire duration of the Project. quantity) X.1. List of proposed constraints in the schedule with Justification (subject to approval by HIB/AECOM) vi.PDF for narrative and barchart) and can initially be made via e-mail. unit. 4. ii. Use different colors for non-critical activity bars.
Finish 3.docx Page 5 of 5 7/19/2009 12:13 PM .P6 TECHNICAL GUIDELINES viii. P6 TECHNICAL GUIDELINES v1.1. The AECOM PM may from time to time direct the CM and/or the contractor to submit additional reports as required to facilitate proper review and approval of the schedule.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.