Activity network diagram: Difference between revisions
(Infobox update) |
(The LinkTitles extension automatically added links to existing pages (<a target="_blank" rel="noreferrer noopener" class="external free" href="https://github.com/bovender/LinkTitles">https://github.com/bovender/LinkTitles</a>).) |
||
Line 32: | Line 32: | ||
==Methods of construction== | ==Methods of construction== | ||
To construct the '''activity network diagram''' the two methods are usually used. The '''activity on arrow''' method and the '''activity on node''' method. The most commonly used method is the latter one - '''activity on node'''. The stages of implementing the '''activity on arrow''' method described by Ron Basu as follows (Basu R, 2004, p. 129): | To construct the '''activity network diagram''' the two methods are usually used. The '''activity on arrow''' method and the '''activity on node''' method. The most commonly used method is the latter one - '''activity on node'''. The stages of implementing the '''activity on arrow''' method described by Ron Basu as follows (Basu R, 2004, p. 129): | ||
# ''Assemble the project team with the ownership and [[knowledge]] of key tasks''. | # ''Assemble the [[project team]] with the ownership and [[knowledge]] of key tasks''. | ||
# ''List the key tasks with brief description of each one''. | # ''List the key tasks with brief description of each one''. | ||
# ''Identify the first task that must be done. The tasks must be done in parallel and the sequential relationship between tasks''. | # ''Identify the first task that must be done. The tasks must be done in parallel and the sequential relationship between tasks''. |
Revision as of 23:11, 19 January 2023
Activity network diagram |
---|
See also |
Activity network diagram is a control tool used to establish and observe the most adequate path, also known as the critical path, and also a pragmatic agenda for the finalization of a project. The diagram is displayed graphically, describing a brief picture of all assignments, their sequence, their predicted completion time and the activities that could be completed simultaneously (Basu R, 2004, p. 129).
An activity network diagram is often referred to as:
- Pert (project evaluation and review technique) in some alternations;
- Cpm (critical path method);
- a precedence diagram;
- network analysis
Application of the activity network diagram
In the 1960s and 1970s the activity network diagram was broadly implemented in most projects. The more complex larger projects got, comprising plentiful tasks, the faster its popularity by manual methods started to decline. However, with the arrival of software systems like Ms Project and Primavera, its application at the more advanced stages of the project has increased extremely (Basu R, 2004, p. 129).
Benefits of the activity network diagram
The activity network diagram provides couple of benefits to the table. Some of them are (Basu R, 2004, p. 129).
- The team members can envision seriousness of primary tasks in the overall realization of the project;
- It outlines the problems of bottlenecks and unrealistic schedules;
- It grants facilities a possibility to review and regulate both the resources and the timetables for explicit activities.
Methods of construction
To construct the activity network diagram the two methods are usually used. The activity on arrow method and the activity on node method. The most commonly used method is the latter one - activity on node. The stages of implementing the activity on arrow method described by Ron Basu as follows (Basu R, 2004, p. 129):
- Assemble the project team with the ownership and knowledge of key tasks.
- List the key tasks with brief description of each one.
- Identify the first task that must be done. The tasks must be done in parallel and the sequential relationship between tasks.
- Draw arrows for each task which are labelled between numbered nodes and estimate a realistic time for the completion of eash of these tasks.
- Avoid feedback loops in the diagram. Unlike Gantt charts, the length of the arrows does not have any significance.
- Determine the longest cumulative path as the critical path of the project.
- Review the activity network diagram and adjust resources and schedules if appropriate.
References
- Basu R, (2004), Implementing quality: A practical guide to tools and techniques: Enabling the power of operational excellence, Thomson, Great Britain
- Rumane A.R, (2013), Quality tools for managing construction projects, Crc press Taylor&Francis group, Usa
- Rumane A.R, (2016), Handbook of construction management: Scope, schedule, and cost control, Crc press Taylor&Francis group, Usa
- Urdhwareshe H, (2011), Six sigma for business excellence: Approach, tools and applications, Pearson, India
Author: Jakub Winiarski