Activity ID code

9 out of 10 times I use the Act.Id Codes as an extention to my activity codes. In shutdown enviroments I (P3 actually) use the first two characters for the Area id (or what P3 calles the Subproject or Project ID), then I use 5 characters for the workorder id (last 5 character from that) and the remaining 3 characters to identify the type of work.

For that last, here’s an example:
101 = Build scaffolding
102 = Remove scaffolding
105 = Remove Isulation
106 = Apply insulation

We tent to group the disciplins in the last 3 characters:
001 - 100 : Production department
101 - 299 : Civil works
300 - 599 : Static
600 - 700 : Rotating
and so on

This way we can easily filter all scaffolding taska w/o using a 3 character code in the Activity codes.

Hope this helps.

Wallace,

Marc has given you some of the ’how’. Now for some of the why. The key to a good schedule is good logic. Having structure in the ID helps you quickly and easily make logic connections. Nine times out of ten you will know the first 6 or more ID characters because of the coding structure you have built into it. You (in P3, anyway) simply type in the six+ characters you know and the hypertext list jumps to the top of the activities that match, making selecting the one you want quite easy (as P3 displays the descriptions also).

The trick is to include in the ID things that help and that you are not likely to need to change during the life of the schedule, as constantly changing ID’s is not helpful (just ask a ms project user!).

Making use of the coding in your (P3) layouts is also possible.

Regards,

Robert Turner

Hi,
fist of all, marc pointed out some certain numbers for certain trades. is it a standard practice (Number used for certain trades e.g. Scaffolding-101) and do the trades have such differenciation between them. if so, can you plese guide me to the schedule showing such catagorical differenciations.
Regards
Safdar H. Hashmi
07782309793,
United Kingdom