Float belong to the owner
Forum Sponsor
Top Posters
Julian Pegg
1 posts
Peter Nagy
2 posts
Raymund de Laza
17 posts
Syed_Asad
0 posts
Tony Greyvenstein
0 posts
Ahmed Al-Jubouri
13 posts
Umar Alvi
3 posts
Sibusiso Mahlalela
0 posts
Michael Samanyayi
3 posts
Simon Gumede
0 posts
Se,
Your english is insufficient.
Read behind the line.
if you need brain is small ok
My answer "Im acting in good faith and in fairness".
period
Hope this will make you happy and jumping with joy.
Hi Charlie,
How can we come up with good project management practice that you are saying if you can not even answer direct questions about acting in good faith and fairness?
Se
Gentlemen
This debate has been going on since time disputes started many years ago and it has been a very lucrative topic for lawyers everywhere.
It has also been going on too long in this forum.
An attempt was made two years ago by Keith Pickavance and Fenwick Elliott to draft a contract rider to add to the JCT suite of contract forms. This was called "Time Risk Management" and dealt with all matters relating to how EOT and other related matters were to be dealt with contractually.
Although it was an excellent document I have no knowledge of it ever being used on a project.
I t does howver give a useful guide as to an ideal way forward.
Best regards
Mike Testro.
So Charlie,
Which project u hav worked on wherein it states that FLOAT BELONGS TO THE OWNER or r u suggesting for any of ur new project to hav this clause.
If yes, then plz let me know on whihc project u r working or whats ur company name?
Theres something called, late start and late finish. As contractor is submitting the program, contractor has full rights to work as per late start and late finish dates and no contract person can deny this. If u agree to this statement, then definitely activity owner owns the float rather than client alone.
Cheers,
Rav
Se,
If only you have get involved at the infancy of this thread, you will know that my intention is for the good of project management and for the project in general by providing this cluase to eliminate nuisance from the contractor by throwing premature claims for extension of time knowing that the events happen during the existent of float.
IF you will make a small effort to re-trace how the development of this thread then you will appreciate my effort to be fair to all : "the owner owns the float".
A lot of you guys/gals out there must think of ways for your projects to move forward instead of being bog down arguing who owns the float.
Also to threaten that there will be no contractor to do the job because of this clause "the owner owns the float" only demonstrate the highest level of ignorance"
Hi charlie,
Do you really think that you are acting in good faith by imposing such clause in the contract? If yes, please explain how such clause could be considered fair to both contractor & owner.
I dont think scoring points against a contracting party(contractor) just for the sake of removing ambgiguity would result in a smooth administration of contract.
Cheers,
Se
Rap,
It is not yet time to move on....
Because it is still not clear in the contract "WHO OWN THE FLOAT"
AACE to a lesser extent to the point of nuisance SCL EOT protocal or your belove PMI PMBook are only guide. It does not replace what is in the contract.
And to remove ambiguity "THE OWNER OWN THE FLOAT" if ever place in the contact, otherwise, it will only create chaos in project implementation.
Mike,
If you said is true,
Then,
Convince the planning planet world.
This can be done by telling us your experience in a constructive way, or by example or by your post (convincing way).
i guess it can only become a shared commodity (network float) if it exists (if there is an Approved Program) and only during the execution of the project, what after the completion of the project? i (still) cannot believe on as-built float(s).
Hi Charleston
You are not the only one out there pitching for the client. There are two sides to every dispute and in my experience its the owner who can pay for the most expensive - and by implication better - experts.
I spent a lot of time in Hong Kong representing the owner of the New Airport defending against contractors who had genuine claims to present.
Best regards
Mike T.
My alternate email:
[email protected]
To All Owner and Client,
My contact details:
[email protected]
Tel No.: +971 50 896 7079
Remember, Im the only one who can protect your interest.
The rest are sympahetic to the contractor.
My credential: I worked with the contractor side for more than twenty years. I know their mentality, I know how they worked, I know their illussion, dreams and fantassy
Presently, I work in project management. We are successful for there is only one driving force "SUCCESSFUL PROJECT MANAGEMENT"
Charlie,
I’m not sure what point you’re trying to make here. Are you saying that if the client asks for a variation in the original scope of the project they won’t be asked to pay for it either in time, money or both? I can’t see it happening myself, but I’m willing to be persuaded if you can offer examples, instances where changes in the scope by the client have not incurred additional costs in one form or another.
You then say “Not an absolute truth. This is not knowledge because it generalize an events without going into details. This is hearsay/selfish/decietful.” Since generalising without going into detail is something that you seem to do a great deal, I’m prepared to take your word for it.
You then ask, "what if the variation is initiated by contractor?" Well what if it is? If it’s offered to the client and the client accepts the variation because it gives them an advantage then the client should logically expect to pay for it.
You may possibly have wandered off the point a bit when you ask about delays. If there are delays which are directly due to an action or inaction on the part of the contractor, I can’t see that it matters if there has been a variation in the scope or not; provided this variation has been accepted by the parties involved, any delays would be covered by the existing terms within the contract.
You then went on to state that you would protect all owners or clients from “this kind of contractor with this kind of mentality.” What kind of contractor is that, Charlie, the sort that expects to be paid for the work they do? Maybe it’s the sort that expects their client to realise that if they change their mind part-way through a project it will cost them in time, money or both.
Chris Oggham
"Any chang to the original Scope is a variation and the CLIENTS PAYS EITHER BY TIME OR MONEY OR BOTH!"
Not an absolute truth. This is not knowledge because it generalize an events without going into details. This is hearsay/selfish/decietful.
What if the variation is initiated by the contractor, contractor initiated variation?
What if there is a float in the variation???
What if there is concurrent delays with multiple events due to fault by the contractor????
Have you done a forensic delay analysis???? to support your genralize claims????
To all owners or clients, call me if you have problems with this kind of contractor with this kind of mentality. Ill always be there to protect your interest. I know the tricks, very simple because I have the experience.
Sensei
Successful Project Management Consultant
Hi Mr. Raf,
As a clarification, you mean you are one of the persons who did PERT? Its really an honor to know one of the guys who took part in writing one of the major text books of our industry...
Raf, the Polaris missile project was a very huge project. Is it okay if I ask you a copy of your notes, even a level 3 or 4 timeline of the project (portion is ok)? Perhaps, you could share with me any article about the project most especially if it contains the issue about floats?You dont have to lecture about forward/backward pass...
vty,
Arman
:-)
Rav,
I think youve got it spot on.
Chris Oggham
Dont know about the small size projects. But, i m pretty sure, for large size projects, that if client wants to work with a good contrator and if client puts this statement / clause, then contractor will definitely say "**** OFF".
There r plenty of jobs available in market and contractors r now very choosy in selecting it nowadays. Some people still live in those recession days when client was king and can get some extreme clause in the contract. Hey buddy!! wake up, this is 2008 and not 1978.
Float belongs to the project and if client / consultant is smart, then they can minimise the float in the program, but cannot take on grant, it belongs to them.
The argument of the client is that there was a float to squezze the instruction to vary the work. This is cover in standard contract.
However, the contractor contend that due to this variation, he was not able to finish on time.
Contractor logic is ????????
Take note that forensic schedule analysis will reveal that the event "instruction from the client to add a new bay" will not impact in the cpm because of the float.
The contractor can not cite the said variation as causation in project delay.
In conclusion, the contractor will be penalized due to delay not attributed to the instruction "to increase the number of bays" considering that there was a float
The owner owns the float.
The question is:
Should the employer be open to pay damages to the contractor at a later date for acting on and using what the contractor has told him?
In this case, using the float that the contractor has told the employer is available due to his chosen method/sequence of work.
Trevor,
The clients half baked ideas on what can be squeezed in is based entirely on what the contractors current programme is telling him can be squeezed in, thats the main point of this discussion.
The programme shows in detail the time for the erection of the first 40 bays, allowing some further time for an individual bay to that shown the employer has fairly and reasonably estimated the time for this extra bay from the information in the contractors programme.
Trevor
I’m away for the rest of the week so won’t be able to reply but -
If you want to stick to the original contract, why agree to use a contract that allows extra work to be instructed?
For the sake of this discussion, lets say the employer wants an increase the size of a 40 bay steel framed single story building he’s having built by adding one more bay to the end of it. At this point, no M&E or finishes, just wants the extra bay erected and clad to possibly expand into at a later date because his business is now doing unexpectedly better than a year ago when he planned this new building.
It’s an increase in work content which can be accomodated by the float as indicated by the contractors programme when instructed, but certainly not outside the scope of the original contract variation clause.
OK, Ill be in it. There are so many things wrong with this scenario that it is hard to know where to start.
Lets call them the client (hes not really an "employer") and the contractor.
First of all, these two deserve each other and any consequence that follows.
They should have made a contract which described what was being promised and committed to, and by whom, and then stuck to it. Otherwise, the whole concept of a contract is undermined.
The right (a tenuous one) to instruct extras is not there so that the client can just dream up stuff on a whim to add to the scope. If I go into a fruit shop and agree to buy an orange for $1, I cant then just insist on a few grapes as well.
The clients judgement or half-baked opinion about what can be squeezed in or not and whether that affects the contractor is irrelevant. If he wants to conduct the project planning and the construction management, he should have done so from the outset (like owner-builder) and not bothered to hire the contractor.
The contractor should have reminded the client to stick to what was agreed in the first place, and if pushed should have insisted on both money and time.
Thats enough provocation for now.
yup...i have been in this situation where the progress S curve rising like rocket but the critical activities have so many interfaces.
Think I’ll play devils advocate for a moment:
The contractor submits a programme, the CA approves it. The employers business is doing better than expected so he decides ha can afford a few additional things built. He looks at the contractor’s current programme update, (which is currently telling him the contractor will finish on time), and works out that he can instruct some extra work and the contractor can fit it in without it affecting the completion date due to the float available.
On this basis, (that completion is unaffected), and in complete reliance of what the contractor’s current programme is telling him, he instructs the additional work.
The contractor happily does the additional work and gets paid for it but later in the project, due his own fault, the contractor gets behind. The contractor now claims that if the employer hadn’t instructed the additional work he wouldn’t have fell behind because he would have had the float available.
Why should either the employer be penalised or the contractor benefit from this situation?
I believe that during the initial stage of the project float(s) doesnt exist. How can you own something that does not exist?! or how can you own something that is not even calculated yet? And even after the calculation of float(s), its not certain if it would be acceptable! ...by the way, who made the calculations?!!!
You people out there
are lost soul in project management
the simplistic way to finish this discussion is to place in the contract
"THE OWNER OWN THE FLOAT"
Plains and simple
And you will get a very reasonable CPM grom client\s contractor.
no more bulldhitting around, no more zero total float
Guys
As one of the folks who was there when CPM was invented and then PERT I cannot agree that float belongs to the client.
Going back to when we wrote the original Arrow Diagram software we already were considering the scheduling of resources using float. Total Float is the result of the maths within the various paths in the Arrow (now Precedence) Critical Path Networks.
PERT was created in conjunction with Booz Allen and Hamilton back in 1957 for the Polaris Missile project and was specifically created to handle estimating doubt (risk ! )The Total Float and the Free Floats (both Early and Late) and Independent are the resul of the maths.
I was both in the US and UK where in the UK International Computers and Tabulators (who are known as Fujitsu) developed 1202 Pert in 1959, 1300 Series Pert 1961, OPUS, APPRAISE, 1500 Series PERT, 1900 Series PERT, etc etc
All produced Resource Schedules which analysed the resource limitations defined. Critical Activites are scheduled immediately and may or may not overload the resource. Activities with float would be delayed if by assigning the resource, it would go into overload.
Many learned discussions in the Operational Research Society - where as a knowledge area we used to be included with, defintely came out in support of the fact that the Client cant possibly own the Total Float, because the resource scheduling algorithm would utilse it and besides the value of the Total Float was and still is TOTALLY dependent on the forward and backward pass - I hope to God I do not have to explain Forward and Backward passes.
Most PC based software does not provide the user with late frre float and independent float values, or do not make it obviously for the more learned and skilled of our P & S folk.
So the Total Float belongs to the Network. NOw ! who owns the data and results from the network is another ball game
Raf
Hi Armando
Thanks for bringing this debate back to basics.
I remember doing those CPM networks using pencil and graph paper - not even calculators in those days. A forward and backward pass would take an hour or two.
Primavera was - I beleive - the first computer programme to take over the calculation process but plugging in the data was still a tedious process.
P3 has not moved on much since then.
Best regards
Mike Testro
Hi Guys,
While looking for something else entirely, I mis-typed a search term and got this article.
I found it quite interesting, although it may pose more questions than it answers.
Chris Oggham
Anoon,
I agree with you. As for me it is also better if we take a look back a little of history why PERT & CPM were developed.
I reviewed few of my notes...It was in the later part of the 1950s that the U.S. Navy Special Project Office & the consulting firm of Booz, Allen & Hamilton conceptualized PERT in the efforts of the US Government to speed up the Polaris Missile Project. PERT concept stressed probabilistic activity time estimate because the field in which it was developed was typified by high uncertainty. In 1956, prior to the development of PERT, the Critical Path Method was developed by J.E. Kelly of the Remington Rand Corp. & M.R. Walker in an efforts by commercial industry to make an advanced scheduling & cost control methods. CPM originally made no provisions for variable time estimates which is in contrast with PERT but in the conceptual analysis, most of these differences were relatively minor.
Therefore, for me, both conepts PERT & CPM were developed for the benefit of the client / owner.
In my opinion, based on the above, the durations of the activities in the critical path is not a fact. Or, it is not beyond reasonable doubt being based either on a certain level of uncertainty & variable time estimates.
For me, both the contractor & the owner shares ownership & responsibilities of the floats both in the original path & the floats that are generated during project implementation either positive or negative floats.
Thus, should the contractor fails to manage his part of the path, LD will be charged against him. On the other hand, if it is the client who fails, the contractor may claim for EOT & among other applicable claims in accordance with the provisions of the contract.
I have a question guys, I know this is out of this thread but sorry for this...If PERT & CPM were developed by the US during the cold war, what method did the Russians used?
Regards,
Arman
I think its better to discuss about the practical determination of float(s) and not the ownership of it, as float is subjective so as the project.
If the project belongs to the client, and float(s) belong to the project, who has the responsibility to determine float(s)?!!! The Client or the Contractor?
I believe that it is always the contractor whos responsible for preparing the detailed program/schedule based on his methodologies, and therefore plays with the float(s). But! the program always needs approval of the Client! so as the float(s)!
First and foremost thing,
It is not necessary tat all activities with zero float will be on critical path. At least CHARLIE shud know tat or is he like a consultant who tells u time by looking into ur own watch. Just refer to Ronald Winters paper on Longest path. Its explained beautifully.
Neway, Instead of putting this funky statement into the contract, y there is a need to approve a program with float then. Cant client / consultant will make changes in the program and will bring the program with almost zero float before approval. I dont need to tell here to make a program with zero float. Its all possible.
Has somebody locked someones brain as these foolish ideas are poping out.
With such a booming market and with so many jobs flowing around, which contractor would like to work with a client / consultant who will force u to make a program with zero float or yelling OWNER BELONGS TO FLOAT.
Cheers,
Ravi
Guys,
It is very educational to read all your comments. Be rest assured that I or probably other PP members have valued your comments. Thanks guys.
Regards,
Arman
We do.
Unless stipulated otherwise in the contract, the float belongs to the project.
Whether the Owner, Client, Contractor or Sub contractor want to claim it, at the end of the day all considerations will be given for the benefit of the project objectives.
Chris is right. If it was just that simple, we should not be having this discussion for several years now I believe, in planningplanet.
Charlie,
Who invited you anyway? It was just an information for those attending. Simple. Trying to be smart again?
cheers,
Anoon
Take note that if contractor will prepare cpm without float then all activities are critical.
if one activity is delayed than the project delay
and if delay by contractor is concurrent with owner delay, then, there is no eot entitlement.
Contractor will lost everything
what im trying to say is for the contractor to be reasonable in preparing cpm to minimize not eliminate the use of float.
"everything is negotiable" contracts are negotiable, but I believe (always)that during the drafting of the contract there is no detailed program/schedule that determine(s) the float, so nobody ever notice or give importance to floats (who cares!)how can you practically determine float(s) on EPC projects?!!!
if you include in the contract, that the "Owner owns the float", then it is supposed to be considered that the owner had prepared the detailed program/schedule and is confident that such is feasible in order to negotiate with probable contractors. If that is the case (if im on the contractors side) ill see to it that im going to prepare a program/schedule without any float!
BUT BUT BUT
WHY CANT WE JUST INCLDUE IN THE CONTRACT
"THE OWNER OWNS THE FLOAT"
WHY????, WHY???
I worked in the project management consultant. What professional bias will I be charged if I will advised the owner to include "THE OWNER OWNS THE FLOAT"
Am I doing a desrvice to the project management practice.
Or it will take a lot of tiime for any project mnagement institute to revise there books or idea by simply stating "THE OWNER OWNS THE FLOAT".
The contractor can say no to any of the owners terms and conditions. Everything is negotiable.
The contractor should especially reject, if necessary, the owners arbitrary contract finish date in favour of a feasible finish date based on what it will take to do the job.
Trouble is, most contractors will sign up to a contract finish date without having done sufficient planning prior to signing the contract to know if the contract finish date is even feasible, possible or achievable, and usually discovers too late that it is not. There was never enough time to do the job, never any float in it, in the first place.
There may be float in the non-critical paths (where else could it be?) and the owner may think he can add in variations (change his mind etc)into the non-critical paths withou this having any impact on the contractor or his ability to meet some target date (ie the contractor justr has to cop it). However, any float that is there is part of the contractors general reserve against various risks, known and unknown. Using it up has predictable consequences.
CJ-O says something profound:
"indulging into stupid debate as to who really own the float"
Yes, it is. Regardless of what legalistic nonsense either party can jam into the words of the contract and force feed to the other (slightly more gullible) party.
Hi Guys,
Charlie has made the point clear and simple that - All the owner has to do is to place in his contract with the contractor that "THE OWNER WILL OWN THE FLOAT".
But then again if it was really just that simple, "Who owns the float", would not be one of the topics under discussion at 52nd Annual Meeting of AACE International & 6th World Congress of ICEC in Toronto.
While Charlie has suggested an approach to the difficulty, what happens if the contractor says "No" to a contract with such a condition specified?
Chris Oggham
See
no need to attend.
All the owner has to do is to place in his contract with the contractor that "THE OWNER WILL OWN THE FLOAT".
Plain and simple, no complication.
Whatever this means to the contractor who generally preparet the project cpm schedule, let the contractor elaborate.
It is the owner prerogative to protect his interest and to stop any discord within the project team by indulging into stupid debate as to who really own the float.
The other advantage to this approach is for the contractor to seriously evaluate his cpm and to minimize exessive and unreasonable float, knowing that he can not manipulate the client regarding the issue of float.
This is for all those planning to attend the 52nd Annual Meeting of AACE International & 6th World Congress of ICEC in Toronto. There will be a technical topic which will discuss/debate the subject of "Who owns the float".
Precisely because no two contracts are exactly the same, (even apparently standard forms are usually customised versions), that there will never be a single right answer. The best we can do on here is talk generally about the topics, the right answer for a given contract will depend on the contract itself.
Time is universal to all of us, theres no reason why there cant be a universal extension of time clause, at least in its general principles but with customisable risk allocation to suit each project. Then we would all know where we stood on every project - but this is dreaming as it will never happen.
Its seldom you encounter a programmes critical path at the onset of the project will be the acceptable critical path for some of the reasons below:
1. The planner plugged-in buffers. Long durations.
2. Constraints were unnecessarily assigned.
3. Crewing is not clear. e.g. 4 people in one crew, 6 people in 1 crew.
4. Terminal float.
5. Inadequate details in schedule.
6. Is the acceptance of the programme by the clients CA bound him contractually?
The above and maybe more combined with contract stipulations or absence of stipulations(Contractor has the obligation to mitigate project delay, Best endeavours)adds up to the confusion on how eot, mitigation, acceleration, ownership of float should be resolved.
If theres one contract that connect all these dots, it would certainly much easier to come to an agreement. But unfortunately, for whatever reason, contracts I have encountered lacks one or more of the above.
No wonder, even in this thread, we dont have an agreement yet.
Raviraj,
Sorry I dont have a copy but Ronald posts on this site and so you could contact him directly through the site.
Andy
Andy,
BTW do u hav ronalds paper on Longest Path now. I lost somewhere. If u hav, wil u plz paste the link here.
Cheers,
Rav
Charlie,
Critical is normally taken to mean that demonstrated to be on the critical path of a programme in a CPM analysis and I would agree with Ronald that this is the longest path dictating the completion of the project.
If sectional completion dates are involved then it is the longest path of activities dictating the completion of each section AND the longest path dictating the completion of the project. Using zero float as a measure of criticality is useless if the programme is full of constraints. Constraints are usually one of the first things any analyst will look for in a programme to see where the contractor has been trying to prop up his case.
That said, as a recent Scottish case showed that accurate CPM analysis is not always possible and a number of activities could be thought of as being "critical to completion" although they would not all show up as being critical in a CPM analysis. ie, it was obvious that completion was delayed by these events such as variations to the scope of work given after the current completion date had passed.
Most contracts tie the entitlement of an eot to an employer liable event that has caused a delay to the completion date. I’ve been involved in some contracts that didn’t and the discussions and debate become pretty lively then. But normally, if the event doesn’t cause delay to the completion date then there is no entitlement to an eot, although disruption might be claimable.
The eot is normally the period of delay equal to the delay to the completion date, not the duration of the event itself – hence float amongst other things is taken account of. I’m ignoring those contracts that give entitlement to an eot for “likely delay” rather than “actual delay” such as the JCT conditions.
So when determining what the eot should be it is a case of working out what the events affect on the completion date is, not the event lasted for 60 days therefore the eot is 60 days.
But like everything we discuss on here, the devil is in the detail of the contract wording. This will define under what circumstances entitlement to an eot arises and what needs to be considered in working out the period of the eot.
If your contract does tie any entitlement to an eot to the delay to the completion date then your contractor can not just say “I plan to start but I can not start so I was able to start after 60 calendar days, therefore, as per delay analysis as built as plan: I’m entitled to 60 calendar days”.
Critical Delay Caused: This can be derived from as-built programme. Ownership of float question comes only during entitlemnet of extension of time by contractor.
Ownership of float depends upon which method u r using to demonstrate entitlement to own the float. The method depends upon the evidence available, existing progrtamme evidence and particular circumstances. There are mainly only two methods, of which there r different variants and hybrids given different names (Impact as-planned, as-planned v/s as-built, as-built but-for, collapsed as-built, time impact method, window slice method).
Method of analysis will b means of demonstrating causation and inevitably and this will be theoretical based on disputed facts and opinion, even though u r using as-built method.
The method of analysis using as-built programme has d advantage that it creates accurate record of actual progress if based on traceable evidence. In practice, it is necessary to focus the analysis on key areas of delay to avoid unnecessary expense. This makes the method iterative. It is not usually sufficient to simply compare the as-built programme to the planned programme without verifying the planned programme. It is necessary instead to prepare a construction logic which explains the sequence of events and reasons for the actions taken and delay caused.
The method of analysis using time impact or snapshot approach requires base programme initially adopted by the contractor to be updated for each event. The update requires the construction logic to be examined for any change with new activities created if necessary and the durations re-evaluated. This update may create a new critical path and an extended period. The updated programme is then updated for the next event and so on. If data is not available at the time of the delay then another method needs to be used. The advantage of this method is that it records the unfolding of events and places actions in context.
Ownership of float is not a weekly meeting issue and will be raised only during EOT claims. Whatever method is adopted, it is necessary that the expert preparing the programme understands the construction issues involved as well as the limitations of the particular programme software and the method. The expert must also be able to explain the analysis to allow the judge, arbitrator, and adjudicator or A/E to understand.
Cheers,
Ravi
Pagination