Differences in critical path calculations

[pmkb]

Modern scheduling software employ much more sophisticated algorithms and considerations (multiple calendars, disjoint resources, etc.) than available published definitions for ADM and PDM critical path networks cover.

Differences exist in how software vendors approached some of the problems inherent in expanding the original definitions/algorithms leading to project management software that calculates the same logic network with different results.

Is it necessary or desirable for PMI, AACE, ANSI, IEEE or some other industry authority to set a standard for calculating schedules?

[pmkb]

Looks like the PMI College of Scheduling is taking the initiative:

Scheduling software has evolved over a 50-year period. Without the benefit of coordinating standards, different software products were designed to meet the needs of dissimilar user markets. Some programs, wishing to distinguish themselves, have even introduced their own lexicons. Today, there is insufficient consistency between scheduling software packages. There is even broad disparity in how various programs perform basic scheduling calculations. These two conditions, alone, justify the engagement of Software Enrichment.

Scheduling Excellence Initiative - Software Enrichment

[Bernard]

Differences exist in how software vendors approached some of the problems inherent in expanding the original definitions/algorithms leading to project management software that calculates the same logic network with different results.

There is a thread at the Planning Planet, What do you expect? that explores this issue in some depth.