Skip to content

Correct Defination of Level 1,2,3,4 in P3

Vijayendra SurveMember for 19 years 5 months
Created
4
3
0
Sir,
wht is correct defination of levels we mention in contract wht is scope & wht it says...

4 replies

Oldest first
  1. 0
    Dieter Wambach ·
    Vijayendra
    there is no exact definition just a rough common understanding:
    L 1: Management overview, i.e. Key milestones + key-hammocks; about 10 activities with baseline
    L 2: Still an overview but more detailed: e.g. inclusive lead-time for key items, more milestones; still 40-50 activities, depending on size, importance, risk, ... of the project up to 100.
    L 3: All main activities.
    L 4: All activities for a certain topic, e.g. all engineering documents

    BUT if you’ll ask 5 people you’ll probably get at least 10 answers - basically the same, different in details. --> Levels must be defined with the customer.

    In P3 it is very easy:
    Create activity-code e.g. "Level Schedule" with the different levels -->
    Assign a value to each activity -->
    Create filters for each -->
    Arrange page setup for each -->
    Create layout for each -->
    give a proper name -->
    save

    If a collegue did so already, with the transfer button you can easily copy those filters and layouts - access rights assumed.

    Regards

    Dieter
  2. 0
    Carmen Arape ·
    Vijayendra,

    Fully agree with Dieter about asking 5 people and getting 10 different answers.

    I am someone who would like to add something:

    1.- Dieter definition is OK for me. I have minor differences that it might be worthless to mention them.

    Key things for me are:

    Level 1: I try to define Level 1 in alignment with Project manager and Client. My last 3 projects, The Client gave me the Key Milestones as an input.
    At this level I show the Critical Long lead Items (Equipment with critical delivery Time). Very important nowadays with a overheated market.

    Lev. 4: must represent the scope of work. It depends on Project phase, for instance:
    Engineering: activities defined according list of deliverables.
    Procurement: Detailed procurement cycle. Especial attention to split activities when they have different responsible (especially if Client review/approval is involved).

    Construction: always construction in a nightmare for me. If the Construction team has a good planning background, I work with a lot of detail especially for every Construction package.
    If the Construction team does not have idea of planning, I develop a simple schedule more oriented on the progress measurement database.

    Level 2, 3 : It is the roll-up of level 4 in order to inform intermediate management, for instance , Engineering leads, Peocurement leads.

    Cheers
  3. 0
    Oliver Melling ·
    Vijayendra,

    Try looking on the Planning Engineers Organisation website.

    A paper written by Gary France states what should be included in the different keveks of a programme.

    Regards,

    Oliver
  4. 0
    Oliver Melling ·
    And this time with spelling that is slightly better.......

    Vijayendra,

    Try looking on the Planning Engineers Organisation website.

    A paper written by Gary France states what should be included in the different levels of a programme.

    Regards,

    Oliver

Log in or join to reply

ProjectControls.com is free to join. Members can post questions, reply, vote and follow discussions.

Existing members: your original username and password still work. Forgot password?