Vous êtes sur la page 1sur 6

.

'

IA:COM P6 PROJECT ID FORMAT GUIDELINE V.2 As of: 04-Mar-1O

The following P6 Project ID format shall be used for all Project Schedules under this program, This Format should also be used for
P6 for Import/Exports files (.XER) as well as files generated from scheduling software type other than P6,
The Project ID scheme consists of identifiers generated based on program requirements as follows:

Project Type Identifier


The Project ID will use one character for Project Type, The intent is to identify the Project as Housing or Infrastructure,
H - Housing Project
I - Infrastructure Project

Project No. Identifier


The second set of characters is the AECOM Project No" It identifies the Region, the Shabia and the unique Project index number.
1 Region (I-East Region, 2-Central Region, 3-West region, 4-South Region)
01 Shabia (Ol-AI Butnan, 02-Derna, 03-Aljabal Ahkdar, etc.",,)
0001 Project Index Number

Schedule Type Identifier


The third set of characters consists of 3 letters to identify the schedule type
BAS Baseline Schedule
RBS Revised Baseline Schedule
U01 Schedule Update (U01-Update 1, U02-Update 2, etc.",)
REC - Recovery Schedule
TIA Time Impact Analysis

Schedule Revision Identifier


The fourth character of the Project ID will identify the revision
A First schedule submittal
B - First schedule revision (C - second schedule revision, D- third schedule revision, etc.",)

WBS level 1 Identifier


The last character of the Project ID will be the WBS Levell Identifier, which is always the number 1.

Example:
For the following project

AECOM Project No. Project name


1.01.0002 Full infrastructure in city center of Tobruk ~ -
Infrastructure East ~
AI-Butnan

The Baseline schedule project ID will be:

II I 1.01.0002 IBAS I .A I .11


WBS First Level Identifier

Schedule Revision Identifier

Schedule Type Identifier

Project No, Identifier

Project Type Identifier

Consequently, revisions to the baseline will be: ILOL0002,BAS,B.1, ILOL0002.BAS.C.1, etc. .....

Update NO.1 will be: : Il.OL0002.UOl.A.1

First Revision for update NO.1 will be: ILOl.0002.UOl.B.1


Update NO.2 will be: : ILOL0002.U02.A.1

P6 Project ID v2.xlsx 13-May-09 03:30 pm


P6 TECHNICAL GUIDELINES

Version 1.3
As of August 16, 2009
IAECOM

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 used shall be English.

c. IIIII!&I Currency shall be Libyan Dinar (LYD). Follow the guidelines below when creating the currency in P6:

No. of Decimal places: 2


Decimal Symbol: Period (.)
Digit Grouping Symbol: Comma (,)

D. _ Contractors shall use the approved format developing the Project ID for the schedule. This Format will
be provided by the Program Manager.

E. Reporting Frequency: Monthly

F. IJg 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. 11IIIII Retained Logic


J. Hours per Time Period settings shall be:

Day Week Month Year


8 40 172 2000

K. _ 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.

L. 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
(Le., 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 vl.3.docx Page 1 of 5 8/16/200912:21 PM


P6 TECHNICAL GUIDELINES
IAECOM

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

N. Activity Relationships: Assign predecessors and successors relationships to each activity. No open ended activities
will be accepted, with the exception ofthe first activity and last activity in the schedule.

O. 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 (Le. X.xX.xxxx - code description)

P. 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 night
calendars shall be 20:00hrs to 05:00hrs next day.
4. The Contractor shall incorporate any seasonal restrictions within calendars assigned to activities.
S. Calendar shall include all Libyan National and Religious Holidays at a minimum. These Holidays are:

March 2 Jamahiriya Day


March 9 Prophet's Birthday
September 1 National Day
*September 21, 22, 23 Eid al-Fitr
*November 29 , 30 Eid al-Adha

Q.-
'The dates for Religious Holidays are based on the Muslim Calendar and are subject to
change based on government approval and announcement.

1. Create milestone activities for significant contractual events including, but not limited to the following:
I. Contract Award VII. Mobilization
II. Notice to Proceed, VIII. OutsideAgency Coordination
III. HIB Approvals IX. Phasing and/or Staging
IV. ROW Availability X. Interim Contractual Milestones
V. 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 being
allowed 365 days a year and 24 hours per day.

P6 TECHNICAL GUIDELINES vl.3.docx Page 2 of 5 8/16/200912:21 PM



R.
P6 TECHNICAL GUIDELINES

IIIlIDIII The use of constraints is permitted only by written approval from HIB/AECOM Program Manager.
IAECOM

s. !!liThe use of lags is permitted only by written approval from HIB/AECOM Program Manager.

T. Cost and Resources: The schedule sha II be Resource and Cost loaded

U. Activity Resources: Resource loading is required. Labor, equipment and material resources shall be assigned to
each activity in the schedule. Resource 10 shall include the Project number and the description of the resource
(i.e. X.xX.xxxx - Concrete Worker).

V. Resource Calendars: Any calendars related to specific resources (Le., a specific person or piece of equipment) shall
be established as Resource Calendars, with the Calendar name clearly identifying the resource. Resource Calendar
10 shall include the Project number and the description of the resource calendar (Le. X.xX.xxxx - Carpenters 5-day).

W. IIIIlI1!Illnciude a narrative in Microsoft Word and/or Adobe Acrobat format that includes the following
information:
1. General Project Information:
i. Contractor Name
iL Project Number
iii. HIB Number
iv. Project Description
v. Project Type (Infrastructure or Housing)
vi. Region
vii. Shabia
viii. Schedule (i.e. Baseline Schedule, Schedule Update no.l)
ix. Schedule filename
x. Schedule data date

2. Project Metrics:

Contract Start Date Contract Amount


Contract Finish Date Approved Modifications
Contract Duration Current Contract Amount
Percent Complete Payments
Projected Finish Date Remaining Contract Amount
Overall 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 challenges
that may affect the Critical Path.
8. 3D-Day Look Ahead for Major Work Elements.
9. List any problems encountered or potential problems that are anticipated going forward and the
proposed solutions to such problems.

P6 TECHNICAL GUIDELINES v1.3.docx Page30fS 8/16/200912:21 PM


10. Schedule/Logic Changes:
P6 TECHNICAL GUIDELINES
IAECOM

i. List Added/Deleted Activities


ii. 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)

x. 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 ofthe Project.
2. Cashflow Graph. A bar Graph Showing actual and Projected Cashflow for the entire duration of the
Project
3. 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 Codes
S. 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)

y.~
1. The data date for the monthly schedule updates shall be the 10th of each month. Within 5 calendar
dates from the data date, the contractor shall submit the schedule, its narrative and the reqUired
reports to the CM/CS for review. Within 5 calendar days from receipt of the contractor's schedule The
CM/CS will review, approve and forward the contractor's submittal along with the CM/CS Review
Report as shown in the CM/CS Guidance 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 .PDF
for narrative and barchart) and can initially be made via e-mail. 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. The barchart schedule shall include all activities grouped by
WBS. Sort activities by Early Start Date in ascending order. Adjust the timescale on the barchart
portion to show the complete duration of the Project. The critical path activities shall be shown in red
color. 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 ID
ii. Activity Description
iii. Percent Complete
iv. Original Duration
v. Remaining Duration
vi. Total Float
vii. Start
viii. Finish

P6 TECHNICAL GUIDELINES vl.3.docx Page40fS 8/16/200912:21 PM


3.
P6 TECHNICAL GUIDELINES
IAECOM
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.

P6 TECHNICAL GUIDELINES v1.3.docx PageSofS 8/16/200912:21 PM