Managing out-of-sequence activities can be a headache, but this method offers a clear and structured approach to address them effectively. Thank you for sharing this valuable technique!
Thank you for your lecture engg..is this applicable for only started activities or while preparing the baseline at that time can we use this method to reduce the Out of sequence ?
Hi, in baseline there is no out of sequence activities, if there is it needs to be checked Out of sequence activities always generated in updated program as actual site conditions vary from planned You can find videos on "PROJECT MANAGEMENT AND CONTROL by ASIF" which gives definition of Out of sequence activities
Nice video. But one question, why i have to assign SS relationship for the case 3 where successor has been completed already. This SS relationship is with the completed successor activity. Should I not make relationship with any new/another activity?
After importing from excel to P6, while i click on finish i receive a notification of An application event has been intercepted. Please note the event code for reference. Event Code 'TASK-2775-6. Event Time 17-April-24 16:1:49. How to resolve this issue, please help me.
Hi Zeeshan Hope things are well with you، don't worry P6 somtimes have unexpected results which maybe because of General negligence، just check that in your Excel file which you import doesn't contains any formulas means all formulas are converted to values? Always be patient and pay full concentration while import/export in P6، somtimes small things make big issues، good luck
Dear Mr. Ananad, Greetings, In case-3, is mentioned in the video as General Scenario. In special case as you highlighted, it can be simply deleted. e.g. if this milestone is related to acquire all AUTHORITIES APPROVAL to start the work but some certain work is completed without these approval/s means this Milestone is no more applicable to this activity and it can be considered as redundant and can be deleted. I hope it will clarify your concerns, and I will be more than happy to assist you in any further queries.. Thanks & regards
Hello Dear, thank you for contacting, SF is very rarely used relationship type therefore if encounter as "Out of Sequence", the type of relationship should be adjusted to suited with current conditions as SS and/or FF. I recommend to do it manually so that we can understand situation and modify the relationship accordingly. As I am Construction Planning professional, we are using 3-types of relationships (FS, SS & FF) in our design & execution projects, I never encounter for SF relationship. However me too always very keen to know where we can use SF? SF is preferred for (Bottom to Top) planning, means you know the required date and you want to plan for pre-requisite/s for it. In construction field, it maybe that I know when a certain material will be required at site for execution and then i use SF relationship to compute the Plan dates for Engineering & Procurement activities (for example date of submission of Pre-Qualification, material & Shop Drawing submission, order date etc... As far as my work, FS is the best relationship for "Top to Bottom" planning however whenever SS or FF are used, they should be closed with corresponding SS and/of FF with appropriate Lag duration One more reason to avoid SF relationship is that during Update of the project, it may effect the results...
Dear Mr. Anand, Greetings, Sorry for late reply, In general, most of the activities are having more than one predecessors/successors, we need to rectify only relationship/s which causes OoS phenomenon, the rest can be keep remains same because other relationships are still valid. One important point need to understand is that the Number of OoS activities shown in the LOG files includes all these relationship which need to be modified, so once you are rectifying one of the relationship and you notice some other relationships which need to be rectified you can rectified them at the same time instead of going and check the Log files again and again. I hope it will clarify your point, if you need further clarifications please feel free to contact. Thanks & regards
Managing out-of-sequence activities can be a headache, but this method offers a clear and structured approach to address them effectively. Thank you for sharing this valuable technique!
Thanks for commnted please stay connected
Nice sharing
Good sharing
Nice sharing ☺️
very nice sharing.......
Good sharing very nice
wooowww nice sharing........
Amazing sharing
keep sharing such info.........
Informative video
Very nice and very informative
Very nice and good work
Keep sharing
bht allaaaa.........
Very nice to explain thanks sir
thanks brother، stay in touch
Good information for us
Good work........
Thank you for your lecture engg..is this applicable for only started activities or while preparing the baseline at that time can we use this method to reduce the Out of sequence ?
Hi, in baseline there is no out of sequence activities, if there is it needs to be checked
Out of sequence activities always generated in updated program as actual site conditions vary from planned
You can find videos on "PROJECT MANAGEMENT AND CONTROL by ASIF" which gives definition of Out of sequence activities
Nice video. But one question, why i have to assign SS relationship for the case 3 where successor has been completed already. This SS relationship is with the completed successor activity. Should I not make relationship with any new/another activity?
After importing from excel to P6, while i click on finish i receive a notification of An application event has been intercepted. Please note the event code for reference. Event Code 'TASK-2775-6. Event Time 17-April-24 16:1:49. How to resolve this issue, please help me.
Hi Zeeshan
Hope things are well with you، don't worry P6 somtimes have unexpected results which maybe because of General negligence، just check that in your Excel file which you import doesn't contains any formulas means all formulas are converted to values?
Always be patient and pay full concentration while import/export in P6، somtimes small things make big issues، good luck
good work.......
Good information
Good effort bro
nice info...........
Keep it up 👍
good job..........
Good informative vid
Informative
Good information 👍
keep it up..........
Nice video.thanks
While in case 3 predecessor is task dependent and successor is finish milestone i am not able to change to SS relation.. Pl help??
Dear Mr. Ananad,
Greetings,
In case-3, is mentioned in the video as General Scenario. In special case as you highlighted, it can be simply deleted. e.g. if this milestone is related to acquire all AUTHORITIES APPROVAL to start the work but some certain work is completed without these approval/s means this Milestone is no more applicable to this activity and it can be considered as redundant and can be deleted.
I hope it will clarify your concerns, and I will be more than happy to assist you in any further queries..
Thanks & regards
Amazing content
Keep it up bro ☺️☺️
What we do if we have SF ?
Hello Dear, thank you for contacting,
SF is very rarely used relationship type therefore if encounter as "Out of Sequence", the type of relationship should be adjusted to suited with current conditions as SS and/or FF. I recommend to do it manually so that we can understand situation and modify the relationship accordingly.
As I am Construction Planning professional, we are using 3-types of relationships (FS, SS & FF) in our design & execution projects, I never encounter for SF relationship. However me too always very keen to know where we can use SF?
SF is preferred for (Bottom to Top) planning, means you know the required date and you want to plan for pre-requisite/s for it. In construction field, it maybe that I know when a certain material will be required at site for execution and then i use SF relationship to compute the Plan dates for Engineering & Procurement activities (for example date of submission of Pre-Qualification, material & Shop Drawing submission, order date etc...
As far as my work, FS is the best relationship for "Top to Bottom" planning however whenever SS or FF are used, they should be closed with corresponding SS and/of FF with appropriate Lag duration
One more reason to avoid SF relationship is that during Update of the project, it may effect the results...
Thank you
@@projectmanagementcontrol-b8737
I have one doubt can u clarify.. If out of sequence is having more than one predecessor and successor what we will do??
Dear Mr. Anand,
Greetings,
Sorry for late reply,
In general, most of the activities are having more than one predecessors/successors, we need to rectify only relationship/s which causes OoS phenomenon, the rest can be keep remains same because other relationships are still valid. One important point need to understand is that the Number of OoS activities shown in the LOG files includes all these relationship which need to be modified, so once you are rectifying one of the relationship and you notice some other relationships which need to be rectified you can rectified them at the same time instead of going and check the Log files again and again.
I hope it will clarify your point, if you need further clarifications please feel free to contact.
Thanks & regards
Nice video
Thanx For sharing
like it alot........
Amazing
Good
Nice
infomative...........
Goof video
Beauty
Nice sharing
Good sharing
Informative video
Good information
Thanx For sharing
Nice video
Amazing
Nice sharing
Nice video
Amazing
Nice sharing
Nice video
Nice sharing
Nice sharing
Nice sharing
Nice sharing
Nice sharing
Nice sharing
Nice sharing