IMHO, "Loops" are a day-to-day occurrence in any normal EPC project for example. Loops happen (literally) even before the development of any project schedule. Just imagine trying to create a so-called project schedule even before basic and detailed engineering are finished. Isn't the attempt to create a project schedule before Engineering and Procurement are completed is a loop itself? The fact is: Sometimes "Construction" is even started while "detailed engineering" is still in progress in the "drafting board". "Loops" are normal and you can practically live with it. And that's a fact.
Member for
24 years 8 months
Member for24 years9 months
Submitted by Vladimir Liberzon on Thu, 2019-03-14 08:52
Yes, a "Project Schedule" is Everything in ONE. However, perhaps you can just imagine design or engineering works. Of course there are many varieties when creating a design, but you must ultimately come out with one final design. "Scheduling" in concept, should be similar to "Design". The difference is, Scheduling is always variable from start to end (process). And most of the time, Schedules were only copies of previous or similar (failed) projects. Again, just imagine a copied "Design".
Member for
24 years 8 monthsYes Evgeny, and besides it
Yes Evgeny, and besides it models conditional networks (if ... then) and multiple loops if to enter their probabilities.
But the author of this discussion meant Microsoft Project that does not have these capabilities.
Member for
17 years 9 monthsVladimir,I think Spider has
Vladimir,
I think Spider has other advantages to document processes:
1) It has possibility to insert notes/comments for dependencies, so one can put why one process depends on the other one
2) Due to multiple WBSs, it is possible to present the same processes from several points of view
3) You have a Spider Viewer, which costs no money for those, wjo just want to check the process
Member for
19 years 1 monthIMHO, "Loops" are a
IMHO, "Loops" are a day-to-day occurrence in any normal EPC project for example. Loops happen (literally) even before the development of any project schedule. Just imagine trying to create a so-called project schedule even before basic and detailed engineering are finished. Isn't the attempt to create a project schedule before Engineering and Procurement are completed is a loop itself? The fact is: Sometimes "Construction" is even started while "detailed engineering" is still in progress in the "drafting board". "Loops" are normal and you can practically live with it. And that's a fact.
Member for
24 years 8 monthsThe only problem is showing
The only problem is showing Loops.
Schedule shall finish and loops with unknown number of times is unacceptable.
When modelling projects we define the probabilities of the return and certain number of loops that may happen (each with lower probability).
Member for
19 years 1 monthYes, a "Project Schedule" is
Yes, a "Project Schedule" is Everything in ONE. However, perhaps you can just imagine design or engineering works. Of course there are many varieties when creating a design, but you must ultimately come out with one final design. "Scheduling" in concept, should be similar to "Design". The difference is, Scheduling is always variable from start to end (process). And most of the time, Schedules were only copies of previous or similar (failed) projects. Again, just imagine a copied "Design".