Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

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

5 replies [Last post]
Gary Whitehead
User offline. Last seen 4 years 45 weeks ago. Offline

I'm reviewing an MSP programme for a colleague. He is concerned that he can't see a critical path running through the project schedule.

The "critical" filter shows the back end of the path, but not any activities upstream of a critical SS + lag relationship

I think this is because MSP is calulcating total slack (aka float) as finish slack, rather than finish or start slack, whichever is lower.

Is there a setting I can change, so that it will take start slack into account for criticality?

 

Obviously, I can suggest that he replaces the Start lag with an activity, and link them with FS to get around the problem, but I also want to give him the option of a settings solution, if one exists.

 

The project was created in MSP 2010, but I am using MSP 2003 to review it.

 

Thanks in advance,

 

G

Replies

Rafael Davila
User offline. Last seen 52 min 49 sec ago. Offline
Joined: 1 Mar 2004
Posts: 5229

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.

Gary Whitehead
User offline. Last seen 4 years 45 weeks ago. Offline

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

DS Chan
User offline. Last seen 11 years 14 weeks ago. Offline
Joined: 28 Feb 2002
Posts: 3

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

 

    Trevor Rabey
    User offline. Last seen 1 year 21 weeks ago. Offline
    Joined: 29 Nov 2005
    Posts: 530
    Groups: None

    Happy to discuss it if I can see it.

    send it to me:

    trevor@perfectproject.com.au

    Mike Testro
    User offline. Last seen 4 weeks 2 days ago. Offline
    Joined: 14 Dec 2005
    Posts: 4418

    Hi Gary

    Try setting all the tasks to ALAP.

    Best regards

    Mike Testro