Mike
- In that case set up a "Traffic Light" column that will highlight when tasks are within 5 days of turning critical.You will see immediately what calendar they are on - including resource calendars - and can take action accordingly.
Although Spider provides for signals I prefer to use conditional formulas that will provide a descriptive label that at times can be empty. I find descriptive labels easier to understand, colors alone tell me nothing, perhaps because I use a B&W laser printer. I love colors but it comes at a cost for printing, scanning color is no issue.
Filtering for critical and near critical activities is no issue, I mentioned the filter as to expose the need. All activities are placed on the schedule at a specific date because of a reason, even those without predecessor are placed at a date you specify for start of project, maybe I left this delay reason out because in the absence of any other this will govern, can also be delayed by other reasons such as resource availability, date constraint, financial resource availability, but which? I am not interestef in just a fee of the possibilities but also on any that might be left out.
Filtering for criticality alone will not tell you about the origin of the delay reason; if delayed because of a calendar exception this can be hard to figure out it was because of a calendar exception and which one, you need functionality that will tell you unless you can spend a lot of time to figure it out. The software delays the activities for some reason, a reason that might change as you update the schedule, the software knows, why not using the power of the computer?
Each time the software position an activity I do not see why it cannot create a flag to record the reason, if it slows the schedule calculation then it can be optional so when not selected it displays nothing and when selected it displays a delay reason for each activity.
- I see no reason why a sort of long term cash flow calendar cannot be created and applied to the Level 1 summary bar.
In Spider the user can include different objects into resource constrained scheduling: Materials, Cost Components, Material Centers, Cost Centers, Material Sets and Total Cost. Checking required checkboxes enables leveling of selected items.
Spider does not level Summary Bars of any kind, neither WBS Summary Bars nor Hammock Activities, although Hammock Activities can be cost loaded and you can use WBS [phase] priorities to have some control of your resource leveling. WBS Summary Bars and Hammocks move/expand/contract as the child activities move. Therefore you need activities other than hammocks to time your financial constrains to be leveled. An option can be a single activity per WBS but usually you slice your jobs for more detail as to see at what point the WBS is delayed because lack of financial resources. Even on a detailed schedule you do not need to cost load all activities to get good enough slices for your financial leveling. How much granularity is up to your particular needs.
Best regards,
Rafael