Tag Archives: Critical Path Method

The origins of PERT and CPM – What came before the computers!

The development of PERT and CPM as Mainframe software systems starting in 1957 is well documented with contemporary accounts from the key people involved readily available.  What is less clear is how two systems developed contemporaneously, but in isolation, as well as a number of less well documented similar systems developed in the same timeframe in the UK and Europe came to have so many similar features.  These early tools used the ‘activity-on-arrow’ (AoA or ADM) notation which is a far from obvious model.  Later iterations of the concept of CPM used the ‘precedence’ notation which evolved from the way flow-charts were and are drawn.

stockpile

One obvious connection between the early developments was the community of interest around Operation (or Operational) Research (OR) a concept developed by the British at the beginning of WW2.  OR had developed to include the concept of linear programming by the mid-1950s which is the mathematical underpinning of CPM, but while this link explains some of the cross pollination of ideas and the mathematics it does not explain terms such as ‘float’ and the AoA notation (for more on the development of CPM as a computer based tool see http://www.mosaicprojects.com.au/PDF_Papers/P042_History%20of%20Scheduing.pdf).

A recent email from Chris Fostel, an Engineering Planning Analyst with Northrop Grumman Corporation (CFostel@rcn.com) appears to offer a rational explanation.  I’ve reproduced Chris’ email pretty much verbatim below – the challenge posed to you is to see if the oral history laid out below can be corroborated or validated.  I look forward to the responses.

Chris’ Oral History

quartermaster_corpsI was told this story in 1978 by a retired quartermaster who founded his own company after the War to utilize his global contacts and planning skills.  Unfortunately the individual who told me this story passed away quite a few years ago and I’m not sure any of his compatriots are still alive either.  Regardless, I thought I should pass this along before I join them in the next life.  I do not wish to minimize the work of Kelly and Walker. They introduced critical path scheduling to the world and formalized the algorithms.  They did not develop or invent the technique.

The origin of critical path scheduling was the planning of the US Pacific Island hopping campaign during World War II.  The Quartermaster Corps coordinated orders to dozens if not hundreds of warships, troop ships and supply ships for each assault on a new island.  If any ships arrived early it would alert the Japanese of an imminent attack.  Surprise was critical to the success of the island hopping campaign.  The US did not have enough warships to fight off the much larger Japanese fleet until late in the war. Alerting the Japanese high command would allow the Japanese fleet to intercept and destroy the slow moving US troop ships before they had a chance to launch an attack. 

Initially the quartermasters drew up their plans on maps of the pacific islands, including current location and travel times of each ship involved.  The travel times were drawn as arrows on the map.  Significant events, personnel or supplies that traveled by air were shown as dashed lines hopping over the ship’s arrows.  The quartermasters would then calculate shortest and longest travel times to the destination for all ships involved in the assault. The plans became very complicated.  Many ships made intermediate stops at various islands to refuel or transfer cargo and personnel.  The goal was to have all ships arrive at the same time.  It didn’t take the quartermasters long to realize that a photograph of the planning maps would be a devastating intelligence lapse.  They started drawing the islands as identical bubbles with identification codes and no particular geographical order on the bubble and arrow charts. These were the first activity on arrow critical path charts; circa 1942. 

The only validation I can offer you is that by now you should realize that activity on arrow diagrams were intuitive as was the term ‘float.’  Float was the amount of time a particular ship could float at anchor before getting underway for the rendezvous.  Later when the US quartermasters introduced the technique to the British for planning the D-Day invasion the British changed float to “Slack”, to broaden the term to include air force and army units which did not float, but could ‘slack off’ for the designated period of time. 

You will not find a written, dated, account of this story by a quartermaster corps veteran.  Critical path scheduling was a military secret until declassification in 1956.  In typical fashion, the veterans of WWII did not write about their experiences during the War.  No one broke the military secrecy.  After 1956 they were free to pass the method on to corporate planners such as Kelly and Walker.  A living WWII Quartermaster veteran, should be able to provide more than my intuitive confirmation.

This narrative makes sense to me from a historical perspective (military planning has involved drawing arrows on maps for at least 200 years) and a timing perspective.  Can we find any additional evidence to back this up??  Over to you!

Time Analysis Schedule Calculations

There are a range of options for the calculation of dates and float in a CPM network.

I’ve just finished a White Paper focusing on the basic calculations and would appreciate comments on the correctness of the calculations and the methodology adopted.  The aim is to produce a definitive document that is generally agreed. 

You can download the paper from http://www.mosaicprojects.com.au/PDF/Schedule_Calculations.pdf   All comments gratefully appreciated.

Project Planning and Scheduling

The Guide to Good Practice in the Management of Time in Complex Projects (The Guide)  will be published at the end of this year. One of he key messages in The Guide is the need to separate planning from scheduling.

Project planning focuses on creating the project development strategy. It requires experience, vocabulary, communication and imagination and, at its highest level, provides the formula for the logistic strategy for the project construction. Project planning involves decisions concerning:

  • the overall strategy of how the work process is to be broken down for control;
  • how the control is to be managed;
  • what methods are to be used for design, procurement and delivery;
  • the strategy for subcontracting and procurement;
  • the interface between the various participants;
  • the zones of operation and their interface;
  • maximising efficiency of the project strategy with respect to cost and time;
  • risk and opportunity management;
  • the design for the schedule and its reports/communication plan.

Scheduling is a mixture of art and science to create the project manager’s time-allocation tool within the chosen software. It involves the interpretation of the results of project planning to ascertain, amongst other things, the start and finish dates of activities, their sequence and the required resources.

It is not good practice to plan the work whilst attempting to schedule it. Starting to develop the schedule before planning the project is unlikely to produce a satisfactory project-planning solution or an effective schedule.

This is not a new idea! James Kelley and Morgan Walker, the inventors of the Critical Path Method of scheduling in the very first paper published on the subject had the following to say:

A characteristic of contemporary project scheduling is the over-simplification which stems from the inability of unaided human beings to cope with sheer complexity. Even though we know that a detailed plan is necessary, we also know that management need only act when deviations from the plan occur. To resolve this situation we undertook to develop a technique that would be very simple but yet rigorous in application. One of the difficulties in the traditional approach is that planning and scheduling are carried on simultaneously. Our first step was to separate the functions of planning from scheduling.

This is an extract from the paper entitled Critical Path Planning and Scheduling delivered to the Eastern Joint Computer Conference in March 1959, by Kelley and Walker less then 2 years after they had invented CPM. Why is it 50 years later so many planners continue to ignore the wisdom learned from past projects and focus on entering data into computers before they have worked out the optimum way to deliver the project?

For more on the history of scheduling and an abstract of the Kelley and Walker paper see: A Brief History of Scheduling