Can MSP calculate Total slack / criticality arising from SS relationships?

Submitted by Gary Whitehead on
Microsoft Project

Member for

21 years 8 months
Member for 21 years 8 months
Submitted by Rafael Davila on Fri, 2013-01-11 20:44
Permalink

I believe MSP calculates a Start Slack field, try filtering activities with Start Slack </= 0 and/or Total Slack </= 0.

http://office.microsoft.com/en-001/project-help/start-slack-task-field-HP045335790.aspx

If it works maybe you can edit your bars to show criticality. Try with scarlet bar color to identify critical activities because of start slack while red for finish slack or start&finish criticality.

Keep in mind I do not have MSP so I am not able to try how it works.

Good luck.

Member for

16 years 7 months
Member for 16 years 7 months
Submitted by Gary Whitehead on Fri, 2013-01-11 14:39
Permalink

Mike / DS Chan: Thanks for the advice. Setting the activity with SS+lag successor to ALAP, or adding an FF+lag relationship to force the criticality does indeed fix the problem (though at the cost of adding a constraint or relationship to the schedule which may or may not be true), but I am looking for a solution that does not involve making any changes to the activities -only to the way MSP calulates the float.

Trevor: Thanks for the offer of help -I've sent you the file

 

Cheers,

 

G

Member for

23 years 8 months
Member for 23 years 8 months
Submitted by DS Chan on Fri, 2013-01-11 10:45
Permalink

Hi Gary,

''SS + lag relationship'' is not a good pratice for programming, it consists of a open end for the predecessor activity. If use of ''SS + lag relationship'' as logic link, ''FF + lag relationship''  should also be applied for close the path. Please try and see the result.

Best Regards,

DS Chan

 

    Member for

    19 years 10 months
    Member for 19 years 11 months
    Submitted by Mike Testro on Wed, 2013-01-09 16:26
    Permalink

    Hi Gary

    Try setting all the tasks to ALAP.

    Best regards

    Mike Testro