- Original Poster
- #1
Hello.
Firstly sorry this question is a bit long winded. I have tried my best to keep it as succinct as possible.
A small IT project (part of a larger contract our company was awarded in Sept 09) has turned into a large IT project and is causing us some contractual problems.
The specification for this particular part of the project simply stated that our equipment needs to be able to pass data to some 3rd party hardware.
At the time of signing the contract, we had no visibility on the interfacing requirement of the 3rd party equipment (except for the physical connection).
At this stage we should have requested more information or declined to quote hindsight being a wonderful thing
Having finally obtained the specification for the interface in November 2009, and evaluated the task, we found that we have no choice but to commission a programmer to write special interfacing software, as the 2 systems do not share a common interface protocol. Its a bit like trying to connect a typewriter to a washing machine.
This is of course expensive and any marker we had in place for these additional costs will be totally inadequate.
We are trying to make a case to our client that because details of the interface were not made available to us until after we had signed the contract, that we have grounds to justify additional costs to cover the work.
However our client simply refers us back to the one line specification and asks if there has been any variation from it.
Certainly the task description has not changed, but how we now solve the problem has escalated as described.
My question is, do we legally have any grounds to justify additional costs on the basis that the specification was too open ended or incomplete, or do we just take it on the chin?
An thoughts of course gratefully received.
Thanks.
Rob
Firstly sorry this question is a bit long winded. I have tried my best to keep it as succinct as possible.
A small IT project (part of a larger contract our company was awarded in Sept 09) has turned into a large IT project and is causing us some contractual problems.
The specification for this particular part of the project simply stated that our equipment needs to be able to pass data to some 3rd party hardware.
At the time of signing the contract, we had no visibility on the interfacing requirement of the 3rd party equipment (except for the physical connection).
At this stage we should have requested more information or declined to quote hindsight being a wonderful thing
Having finally obtained the specification for the interface in November 2009, and evaluated the task, we found that we have no choice but to commission a programmer to write special interfacing software, as the 2 systems do not share a common interface protocol. Its a bit like trying to connect a typewriter to a washing machine.
This is of course expensive and any marker we had in place for these additional costs will be totally inadequate.
We are trying to make a case to our client that because details of the interface were not made available to us until after we had signed the contract, that we have grounds to justify additional costs to cover the work.
However our client simply refers us back to the one line specification and asks if there has been any variation from it.
Certainly the task description has not changed, but how we now solve the problem has escalated as described.
My question is, do we legally have any grounds to justify additional costs on the basis that the specification was too open ended or incomplete, or do we just take it on the chin?
An thoughts of course gratefully received.
Thanks.
Rob