The coding of the tasks’ID can seem useless but it can allow a better management of the schedule, especially if it is a consequent schedule in terms of number of tasks. Some softwares do not make it possible to code the ID like MS PROJECT, but of others as PRIMAVERA P6 allow it.
I recommend a coding of the ID with the 3 dimensions of the 3D WBS: Zone, Product and Activity, plus an increment. Each dimension can be coded on 3 characters. We should have something of the form: ZZZ-PPP-AAA-0010.
Thus, when PRIMAVERA P6 displays the ID of tasks in the columns predecessors and successors, we can read the antecedents and descendants directly without having to follow the logical links. Schedule becomes more comprehensible. It is all the interest to use this coding of the ID.
The disadvantage of this method it is that planning is heavier to build at the beginning, and its maintainability is effective only if the planner has a table which defines all the codes.
