(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.
Thanks Pat.
CPM oversimplifies, and this has always presented limitations for project management purposes. In particular, CPM has always struggled to represent resource constraints adequately. It also represents all relationships between successive tasks as governed by "hard" logic, when only a minority of relationships are really "hard".
For forensic delay analysis, however, the critical path as a concept still remains necessary to deconflate the competing causes of delay on any given time interval. That is to say, any task NOT on the critical path is deemed NOT to be causative of delay during an interval, on the grounds that non-critical tasks fail the but-for test.
As a deconflater of competing causes of delay over an interval, the critical path does not have any conceptual competition. For this reason, I don't think that, when it comes to forensic delay analysis, that it is going to become redundant any time soon!