I think that it is necessary not only to know logic types but to be able to switch on and off certain logic types.
For example to create several sets of soft logic, try them and select the best set to be applied.
For this purpose it is not sufficient to know if the logic is soft or hard, but create custom logic type like soft logic 1, soft logic 2, etc. or use different names like strategic, etc.
Regards,
Vladimir
Member for
16 years 7 months
Member for16 years7 months
Submitted by Gary Whitehead on Thu, 2014-03-06 08:39
I tend to use 2 divisions: hard logic (which would be your physical logic, plus other mandatory logic such as H&S requirements) and soft logic (which is everything else)
Asta has similar functionality to Spider in terms of ability to assign a category to each logic link. Primavera and MS Project do not. i can't remember how Open Plan handles it.
other than this type of functionality, the other common way of noting logic type is via a schedule narative, which should document such things along with any assumptions, productivty norms, resource limitations, etc used in generating the schedule.
It's not common in my experience for this type of document to be kept up to date as the project progresses, though.
Agree that this info is vital for optimising your critical path, but if the info isn't readily available, I tend to be able to muddle along fairly well working this out by exception for the critical relationships I am interested in. -A decent planner shouldn't have too much trouble working out what is hard logic and what is soft.
Cheers,
G
Member for
24 years 9 months
Member for24 years9 months
Submitted by Vladimir Liberzon on Thu, 2014-03-06 08:16
Member for
12 years 1 monthVladimir, Gary, Mike and
Vladimir, Gary, Mike and Patrick
Thanks for you comments They were very helpful.
Cheers
Richard Carpendale
Member for
24 years 9 monthsThis discussion is very
This discussion is very similar to the ideas underpinning Fred Plotnick’s Relationship Driven CPM. For a brief overview and links to resources see: http://www.mosaicprojects.com.au/WhitePapers/WP1035_RD-CPM.pdf
Member for
19 years 10 monthsHi RichardIn Asta power
Hi Richard
In Asta power project you can also assign different colours and dot / dash lines to different links.
Otherwise you can set up a user ield and just type in the link category.
Best regards
Mike Testro
Member for
24 years 9 monthsGary and Richard,I think that
Gary and Richard,
I think that it is necessary not only to know logic types but to be able to switch on and off certain logic types.
For example to create several sets of soft logic, try them and select the best set to be applied.
For this purpose it is not sufficient to know if the logic is soft or hard, but create custom logic type like soft logic 1, soft logic 2, etc. or use different names like strategic, etc.
Regards,
Vladimir
Member for
16 years 7 monthsRichard,I tend to use 2
Richard,
I tend to use 2 divisions: hard logic (which would be your physical logic, plus other mandatory logic such as H&S requirements) and soft logic (which is everything else)
Asta has similar functionality to Spider in terms of ability to assign a category to each logic link. Primavera and MS Project do not. i can't remember how Open Plan handles it.
other than this type of functionality, the other common way of noting logic type is via a schedule narative, which should document such things along with any assumptions, productivty norms, resource limitations, etc used in generating the schedule.
It's not common in my experience for this type of document to be kept up to date as the project progresses, though.
Agree that this info is vital for optimising your critical path, but if the info isn't readily available, I tend to be able to muddle along fairly well working this out by exception for the critical relationships I am interested in. -A decent planner shouldn't have too much trouble working out what is hard logic and what is soft.
Cheers,
G
Member for
24 years 9 monthsRichard,in Spider Project you
Richard,
in Spider Project you may set any number of dependency types, and then filter, sort, show or hide dependencies basing on custom logic types.
Regards,
Vladimir