“I am writing to advise you that your tender for the above contract has not been successful. The award of this contract was concluded and ran as a further competition…and as such is not subject to the full rigour of the EU rules with regard to an Alcatel Standstill Period. However…the Council intends to follow a standstill period for this particular further competition as it is deemed best practice to demonstrate that a transparent and fair process was followed…The stand-still period will therefore expire1 April 2013 . The Council has decided to award this contract to Liquid Logic… The scores for your tender and the successful tenderer are compared as follows: [Liquidlogic scored 72.09% on the SOR and Pricing and 6.91% on the User Demo against Corelogic’s 64.41% and 6.70% respectively]”
“This price for your tender was£994,965.00 . (The price was for implementation and 7 year on-going costs. The price included the upgrade/fix/patch (managed service), and the discounted “bundle” pricing for 5 interfaces, as these were core requirements as stated in the tender documents. It also included your "goodwill" delay in charging support and maintenance costs.) The price for the Liquid Logic tender was£868,075.00 …”
“Despite your further requests for information, the Council would like to now reiterate it’s position described within the latter sections of this letter, indicating that it feels it has fulfilled it’s obligations under the principles of the standstill period, treated all bidders fairly and transparently and carried out the tender process as stated in the original ITT documentation. Therefore, the Council will not be restarting the standstill period as a result of the latest email request for feedback from Corelogic and intends to conclude contractual arrangements with the winning bidder as planned (midnight 8th April). As previously indicated, the Council will offer an opportunity for a debrief once the standstill period has expired.”
“1. We have been instructed by Corelogic in relation to the Tender and have been passed copies of your recent correspondence including your letters dated 22 and27 March 2013 and3 April 2013 …Your letters suggest that you have provided what you consider to be sufficient information to fulfil your obligations to ensure a transparent and fair process. 2…Whilst Corelogic is grateful for the information provided as to why its bid was unsuccessful, we are writing to confirm our advice to Core logic that the information you have, to date, provided it is inadequate and does not comply with the obligations imposed upon the Council by the Public Contracts Regulations, as amended.. and the general EU Treaty principles of transparency, openness and non-discrimination. 3. The purported award decision notice issued on22 March 2013 is incomplete and does not comply with the requirements of the Regulations. In particular, the Council has failed to provide sufficient information pursuant to Regulation 32 relating to the scores received by either LL or Corelogic, setting out the characteristics and relative advantages of the successful tender to enable Corelogic to understand properly the reasons for the Council’s decision… Flawed Award Decision Notice 6. The 2006 Regulations…provide as follows: Regulation 32 - Information about contract award procedures… 7. The purported notice you have served fails to set out sufficient reasons to meet the requirements of Regulation 32 (2) (b). 8. The test as to what constitutes sufficient reasoning for the purposes of a decision notice and to satisfy Regulation 32 (2) (b) comprises two stages and was set out in the cases of Alstom… and the various decisions in the Dynamiki litigation…This requires contracting authorities to provide all information: 8.1 that would be necessary for the unsuccessful bidder to determine whether or not a decision is well founded; and 8.2 to enable that bidder to have sufficient information to be able to assert its rights before the Court. 9. It is simply not possible for Corelogic to do either of these things for the reasons set out below. 9.1 Corelogic has not been provided with the scores for SOR… 9.2 Corelogic does not know how it scored relative to LL… 9.3 Corelogic does not know the basis upon which it was scored in the "Total Cost of Ownership" section 9.3.1 In complete contrast to the detail provided by the Statement of Requirements Document for the "Fitness for Purpose” element of the Tender, the Council has failed entirely to provide any criteria or scoring methodology for the "Total Cost of Ownership" section of the Tender. It is entirely unclear as to how a bidder could receive full marks for this section, something which would affect how tenders are put together. 9.3.2 Corelogic has no idea why it received a weighted score of 37.75% or why LL was given 43.84% in comparison. 9.3.3 Corelogic has also not been provided with any information about the marks either it or LL received for this section. 9.3.4 In the circumstances, without further information from the Council, it appears that this section has been marked using undisclosed sub-criteria. Again, this constitutes a breach of the Regulations, in particular the requirement of openness, fairness and transparency… 9.4 Corelogic does not know what pricing elements of its bid were used by Bristol to arrive at the figure of£994,965 as being the total price of the contract …9.4.2 Our client’s own analysis of the contract price is set out below, which evidences that the TCO is significantly less than this for 750 users. [There then follows a table which shows this analysis which produces a total of£331,360 ]. 9.4.3 This is highly relevant since, based on the above, and without prejudice to the deficiencies already set out in relation to the lack of scoring methodology for Pricing as set out above, it is highly likely that Corelogic would have been the winning bidder as you have already confirmed that LL’s tender price was significantly higher than this, namely£868,075.00 9.5 The Council has refused to provide further information until the standstill period has expired 9.5.1 Our client has asked you for a de-brief and for further information in relation to pricing specifically. Please confirm that you will provide that in accordance with Regulation 32 (9). Next Steps 16. Given the unfortunate position in which Corelogic finds itself, Corelogic requires the Council’s confirmation, by 11am on Monday,8 April 2013 , that it will now comply with its statutory obligations and will not enter into a contract with LL but will instead: 16.1 provide a full response to the concerns identified above; and 16.2 confirm that it will extend the standstill period to 10 working days after it has provided the information requested above, so that Corelogic has the opportunity to consider this information and consider its legal position. 17. Given the short limitation periods applicable to procurement challenges, we will require the Council to provide its full response to the concerns set out in this letter by no later than 4pm on Friday,12 April 2013 . 18. If the Council fails to provide the above confirmations, by the deadline given above regrettably we will have to advise Corelogic to protect its position by issuing Court proceedings which will include a claim for ineffectiveness and the effect of which will be to suspend automatically the procurement process…”
“Whilst it is not accepted that the general wording of the Claim Form issued originally does not cover those points, the Claimant was advised to propose the amendments so that they could be read together with the Particulars of Claim. The amendments clearly arise from the same facts as the matters referred to in the original Claim Form…”
“26. In my view the just approach is to look at the totality of the documents served. These documents together set out the claimant's pleaded case. There was an obvious mismatch, but in asking whether the proposed amendment was, in truth, an amendment to raise a new cause of action or merely to clarify an internal inconsistency in the pleaded case is, it is proper to look at the pleaded case as a whole. When one does so, it is clear, in my judgment, that what was sought to be done by the subsequent application to amend was not, in substance, to raise any new claim at all, but merely to correct an obvious formal error. I reject the argument that an amendment to correct that clerical error was prohibited by Rule 17.4 and, in my judgment, there was nothing to prevent the court from exercising its general discretion to do justice in response to the application to strike out the particulars of claim. If the circuit judge had considered that he had such a discretion, it is plain how he would have exercised it and, in my judgment, rightly so. I would therefore allow this appeal and restore the action”
“23. The main remaining issue is whether or not there is some good or arguable reason why there should be an extension of time in effect to bring the service of the Claim on30 December 2010 within time. I do not consider there is any such reason: (a) There is no explanation from Mermec as to why the Claim could not have been drafted let alone served weeks before it was served. (b) It is perhaps unhelpful to try to give some exhaustive list of the grounds upon which extensions should be granted but such grounds would include factors which prevent service of the Claim within time which are beyond the control of the claimant; these could include illness or detention of the relevant personnel. There must however be a good reason and none is advanced by the Claimant in this case. (c) It is said that the delay was only some six or seven days and that there should be an extension for such an insignificant period because it is a relatively short delay. However, there is no point in having a three-month period if what it means is three months plus a further relatively random short period. (d) The evidence is however that the Particulars of Claim were drafted and ready to be served on22 December 2010 which of course would, just, have been within the three months period. No explanation has been offered as to why it was not served if necessary by hand on that date or even shortly before . There clearly was no problem preventing Mermec or its advisers from articulating a claim and serving it within a few weeks of23 September 2010 . Even if they hoped to get more information from Network Rail, it was clear from the latter's letter of28 October 2010 that no further information was provided. Certainly, all the basic facts relied upon in the Particulars of Claim were known well before them. (e) It was said by Counsel for Network Rail that if, as appears at least possible, the Claim was served late as a result of some error on behalf of Mermec's legal team, Mermec will have a claim for professional negligence against its lawyers and that should militate against the granting of any extension. I would rather not speculate as to whether there was any culpable carelessness on the part of the lawyers. There are several possibilities, one of which is professional negligence on behalf of the lawyers. Another is that there was a lack of urgency on the part of Mermec in the October to December period. As there is no explanation for the delays, that itself is reason enough to undermine any entitlement to an extension of time. Limitation periods are there for a purpose and extensions of limitation periods should be for good reason; there is no obvious good reason which has been floated in this case by Mermec, which is telling.”