Probality of project being completed on time

Hi Clive,



My hobby is cooking, and most people I have cooked for think my food is very good so I understand your analogy. As a matter of interest, I have two sons, one is a sous chef, and the other one a planner. I have a problem deciding which is the clever one:-)



I worked a project, int the Kalahari Desert in Botswana, where we exceded the 3000 m3 a week mark, it required 4 batch plants, two chillers, a dedicated fleet of truck for getting material to the batching plants (running 24 hours a day), a dedicated quarry and crusher ( 20 km away from the site), a fleet of concrete mixing trucks, a a few other things. What people do not realise is the backup for a this, workshops, maintenace crews,, etc. They ignore these facts, and merrily plan their way through things.



And when you can’t find enough electricians or diesel mechanics, they wonder why the project is falling behind.



Regards



Philip

Hi clive,



As an aside, the old guy and I was wearing identical watches, except his was gold and and mine stainless. Also I am being unfair as he was about five years older than me. I spent twenty years working as an engineer and the last 17 in planning.

Hi Clive,



I am one hundred percent in agreement with you. the problem is that planners need the right experience and tutoring. You are quite right, get the drawings out, and then when you understand the job, structure your project planning. The pitfall is that all projects do not always start of with drawings available, and you then have to sit with the conceptual designers to find out what is in their minds, you then have to structure, keeping in mind the vagueness of the information at hand. The way to do this, and this is what experience is, is to build a structure flexible and robust enough to handle changes, but will survive all.



On your point of using all the team involved, AKA the Thames gates, I had a simular problem a couple of years back, nobody studied the drawings correctly and made some stupid assumptions. I warned them, and they proceded in an incorrect manner and ignored my advice, till some old engineer got hold of some minutes, flew to site, questioned me at length, and realised what I was telling him. We cut 3 months of the program. The draughtsman with the spoon was lucky enough to have people who could grasp his concept.



Regards



Philip

Hi Phillip,



TQ for the constructive comments. Anyway what’s the problem with yu? Seems to be upset.



Thanks



NORZUL

Hi Norzul,



I have a serious problem with risk assessment programmes like Pertmaster and Montecarlo, in that they have no intelligence to review programs and only use basic intelligence to review schedules, this is the so-called clever planners way out. I was involved with a project last year, where pertmaster kept on giving high risk scenarios on my project, and did not reflect the same on other projects, common to the group of projects. However my project finished early and all the others late. This was not the first and the last time, so what does it tell you, that these so called risk programs hve major flaws. They are written by progrmmers, who make certain assumptions about logic, and other parameters, but have no clue about true planning. I wwould like to answer your numbered assesments one by one, as per your numbers:



1: The obvious answer to this is that top management is supposed to have enough experience to make these decisions, The second answer is that you use the expertise in the organisation, to prepare a sufficiently detailed program that top management can believe what they are saying, and demonstrate it in a succinct manner.

2: Obviously 99% of the people are aware of what they are letting themselves in for, so I reject your statement out of hand.

3: That is a bad statement, you obviosly select people with the right experience, or otherwise the thing will fold.

4: the higher the ratio between what????????????????? What is the criteria for a project?????????????? Answer the question, freelance, staf, contractors??????????????/ Never make unqualified statements like this, rather take a leisuirly stroll through an unmapped minefield.

5:PLAIN STUPIDITY.

6:DITTO

7:DITTO

8:DITTO

9:DITTO

10:DITTO

11:DITTO

12:DITTO



Are you a planner or a politician, we have a job to do, and make it as simplistic for other people to do their jobs as possible, why all the negative thoughts, and not something positive, galas



Regards



Philip

Hi Vlad,



As per usual I tend to agree with you, people on projects are probably the key to success, the personalities are critical, there is often clashes, however, this is run of the mill stuff, and there is no room for vendetas and the like, it is important clashes are resolved and the team remains effective. Your comment on rik assessment is valid.



Regards



Philip

Hi Clive,



The point is nothing is impossible, but you have to think it thri\ough thoroughly, as there is always an answer, the cost might be prohibitive, but there is also a mass of constraint, like access, space, material and resource availability, etc. The point is to identify problems, define the problems, and solutions will follow. Always make sure you monitor your float carefully in conjunction with S-curves, as this is your best tools to spot spot problem ares well in advance. Another thing that is is very important, is to interact with the people who have to perform the tasks, and make sure they buy in beforehand. There is so many factors involved, and every project is unique in the problems that crop up, that this is what makes planning probably one of the most interesting fields/disciplines in the world.



Regards



Philip

ps: I am answering the replies individually to keep things in context

Hi Guys,



Norzul,



I am not upset, just my normal self, pointing out the pitfalls in that people believe in the infalibility of computors, and make judgements based on that. As I explained you about the previous project in my posting. What I am trying to say is use your own judgement and experience, and if you are lacking in certain areas, find a mentor with the necessary experience, this could be in the form of of a foreman, supervisor, etc. Good people are always around. Hope this solves some of your problems, and do not hesitate asking if you need some advice, good luck.



Clive,



I agree with you wholeheartedly, maybe you misread something I said, but your example of curing is a good one. Just to expand on it a example: We built a runway in the Kalahari desert, the problems weres massive, with low humidity, wind conditions and temperature. We had to plan around these problems. Sometimes we could only start casting concrete at 23H00 and work till maximum 05H00. We had to plan around these uncertainties. In the Middle East we had the problem of heat, up to fifty degrees celsius, fourty heat exhaustion cases a week, anothe example, critical resources out of action. The point is you have to define the problems and work out solutions, and every project if planned well, with available design information, materials, human resources and correct management has a very good chance of being completed within time. It is all in the mind, and computors are just tools for refling this



Regards



Philip

There are many factors that define project success and many risks that shall be considered. Risk simulation can show what is going on with the success probability - is it increasing or going down during project execution. It is not easy to estimate these trends manually. In the experienced hands this tool is very useful.

There is a problem with Monte Carlo simulation but we discuss approaches, not tools.

We’ve used Pertmaster to cary out monte carlo analysis for the project schedule. I also tried the free trial version of Pertmaster (can download from internet, limited to 26 activities only). Yes, the software is powerfull and very user friendly and will calculate the probability of project being completed on time. But again, as any other software in the market it depends on the inputs and how we establish the linkage between the activities for the project....garbage in garbage out...



To me, based on my experiences the probability of project being completed on time depends on several inter-related factors. The more complex the project the more comlex the factors will be.

FACTORS CONTRIBUTING TO PROJECT DELAY

1) The establishment of the initial project duration or schedule maybe unrealistic but no one dares to challenge that becoz it has been decided by the very top management.



2) Unsuitable contracting strategy. Different projects and situations may require different contracting strategies. It can be EPCC lump sum turnkey project, reimbursable projects, alliance concept project, novation projects, EPCC + PMC type projects, etc.



3) The experience level of the project team personnel inlcuding the contractors, clients, and consultants. The lower the experience the more risk of not completed on time



4) The ratio between the freelance staff and permanent staff for the key personnel in the project. The higher the ratio the more the risk of not completed on time



5) Lack of interfacing and coordination among disciplines (civil&structure, piping, mechanical, electrical, instrument, process) may further contribute to the project not being completed on time.



6) Under budgetted project



7) Inexperience or lack of experience contractor (as a company) in executing the project.



8) Unclear scope of work or project specifications



9) Change requirements introduced by the clients or shareholders e.g. change location of facilities



10) Engineering, procurement, construction and commissioning activities not properly synchronize causing major interfacing problem.



11) Late approval from local authorities



12) etc, etc, etc...

What is strange in the recent postings - people compared calculations and quality of the project team as if they are independent.

Of course calculations shall be made basing on the team estimates and qualification. In this case they may be very useful. And especially because they will show trends in project performance.

In my experience the probability of a project being finished on time revolves around several factors.

Who cast the original contract period or was it just imagined

What standard is the design team

What is the quality of the contractor

If any of these provides a negative response all the monte carlos or monty pythons in the world aint going to bring it home on time.

Oscar

Hi Henk,



Lazy does not imply not thinkng, it implies the opposite

Henk,



As a planner your first mission is to be lazy, but, lazy people find the simplest and easiest ways to do things.

Good evening Philip (goeie avond)



I’ll try pertmaster myself i’ve got a trial.

But to be honest. Most guys who are very lazy come up with the best ideas :-)



After i’ve tried pertmaster i’ll commend on it.

But you’re right once you build a good network you should be able to predict the possibility of the end date yourself. Thats also how i do it now



Kind Regards



Henk

Goeie naand Henk,



The problems that I have encountered with pertmaster is that is is designed to rigidly, and although it will assist you in seeing possible problems,it cannot think. It relies too much on spotting obvious problems, such as constraints and FF dutions etc, that it does not know the thinking behind the schedule. That is why we need experienced human planners who can think logically. Pertmaster is a shortcut for lazy client planners.



Regards



Philip

Maybe you could use Pertmaster.

it calculates the risk and the possibility to be completed at some time.

I never used it myself but i’ve been told it uses the montecarlo system for duration calculation.

Never the les you need a (good) networkplanning to have a reliabel outcome.



www.pertmaster.com



Kind regards



Henk

Hi Vlad/ahmad,



The software becomes immaterial as well as Beta distributions, it becomes a problem of the planners understanding their job and kicking ass. There is no better alternative for projects, than a well qualified planner walking around site, and identifying problems. Computor soft does not do this, and nor does unqualified people.

Beta Distribution, does not even relate nor function.

Ahmad,

please look at http://www.spiderproject.ru/library/mps.ppt

We use this approach but the probability distribution of project results shall be carefully restored taking into consideration the number of activities on the critical path and the total number of project activities.

But even if your estimation was not quite precise it does not matter much if you will manage the project by the trends of probabilities to achieve targets as described in the above mentioned presentation.