CHU Liège adds Mexys’s ‘optional’ connection boxes to its lump sum: 169,400 euros extra, and the two-hundredths lead Mexys claimed disappears
Mexys lost the contract for the computerised anaesthesia record of the CHU of Liège by 79.96 to 81.2 points after the hospital added to its lump-sum price the cost of the Xpresso connection boxes, which Mexys had offered as an option although they were indispensable for the system to work; the Council of State held that the CHU was entitled to add that option price, which Mexys itself had quoted, because the specifications required an all-inclusive lump sum, that it did not have to question Mexys about it, and also rejected the criticism of the evaluation, the demonstration and the free variant of the winner, MEDA.
What happened?
The Centre Hospitalier Universitaire de Liège sought a system for the computerised management of the anaesthesia record (GIFA): supply, installation, commissioning and maintenance, including training (specifications no. CHU/06.33). Under article 1.2.5 of the specifications, bidders had to quote a lump-sum price for fifty software licences and a unit price for any additional workstations, and the lump sum had to cover all supplies and services needed for performance. Mexys offered 474,977.60 euros for the fifty licences and 7,199.50 euros per additional workstation (VAT included). But the hardware needed to connect the software to the medical equipment — the ‘boîtier Xpresso 4 entrées’ and the related interface cable — appeared in its tender as a separately priced option. Because that connection was indispensable in the CHU’s technical environment, the hospital’s services added its price: 169,400 euros for fifty units to the lump sum and 3,388 euros to the price per additional workstation. According to the CHU, the same was done for the competitors. On 18 October 2007 the CHU’s managing director awarded the contract to MEDA, for an estimated total of 564,883.06 euros including VAT. MEDA obtained 81.2 points, Mexys 79.96. Mexys calculated that without the price correction MEDA would have scored 4.18 instead of 5.44 out of 7 on the price criterion (criterion 5), and 79.94 overall — two hundredths below Mexys itself. Its application for suspension under extreme urgency had already been rejected by judgment no. 176.607 of 9 November 2007; almost three years later came the judgment on the annulment action. The Council of State followed Mexys on no point. The specifications required a lump sum covering everything needed; Mexys had itself left out the connection hardware and offered it as an option, so the CHU was entitled to add Mexys’s own option price to the lump sum. The hospital was not obliged to question Mexys first about the scope of its tender, which it had assessed correctly. And Mexys could hardly claim not to understand the amounts of 169,400 and 3,388 euros: they were precisely its own prices for the connection hardware. The other pleas failed as well. The specifications required bidders to demonstrate their software in a European, preferably French-speaking hospital of comparable size; MEDA was allowed to demonstrate at the CHR of Huy, which has five operating theatres. But that obligation was neither a condition of regularity nor a method of evaluating the award criteria, and the evaluation report did not show that it had influenced the decision: Mexys had no interest in that plea. On the criterion of functional richness, MEDA received 36.83 out of 40, according to Mexys seven points more than itself. That Mexys’s tender contained some of the same strengths did not mean they were equally well developed, and the authority did not have to give the ‘reasons for its reasons’. On the integration criterion Mexys actually scored higher than MEDA, so its criticism of MEDA’s ‘single sign-on’ — at MEDA a development on request costing 72,600 euros, at Mexys 8,167.50 euros — could not help it. Mexys’s lower score on the evolution of its software, because according to the tests its anaesthesia-support module would only work with a full-time anaesthetist for one to two years, was not manifestly unreasonable. Finally, the CHU had chosen MEDA’s free variant no. 2: the NAS decision-support module on 36 of the 50 workstations (the only ones able to communicate with it) and a warranty limited to the first year, with a maintenance cost of 137,976.30 euros from the second year. Because the specifications laid down no minimum functional or warranty requirements for free variants, that was not a problem. The action was dismissed and Mexys bore the costs of 350 euros.
Why does this matter?
The judgment shows how a strict pricing rule in the specifications becomes decisive in a narrow points contest. Where the specifications call for a lump sum ‘covering everything needed’, the contracting authority may add to the price an indispensable component that the bidder offered as an option, in order to make the tenders comparable — and need not ask questions about it where the tender itself states the price of that component. For bidders that is a double lesson: whoever prices essential components as options will see their apparently lower price corrected, and whoever challenges that runs into the finding that the correction simply uses their own figures. The judgment also lines up three classic principles that still apply today. A specification requirement that determines neither regularity nor evaluation gives no interest in a plea. An authority comparing qualitative criteria need not give the ‘reasons for its reasons’. And a free variant is tested only against the minimum requirements the specifications impose on variants; if there are none, a variant with less functionality and a shorter warranty can simply win.
The lesson
As a bidder, read the pricing clause of the specifications and include in a lump-sum price everything needed to make the system work in the authority’s environment — connections, interfaces, cables. If you offer such components as an ‘option’, expect the authority to add that option price to your lump sum without asking you first. If you are unsure whether a component belongs to the base contract, ask during the tender period. Challenges to the evaluation of qualitative criteria achieve little if you merely show that your tender ‘also’ had a certain strength, or if you already scored higher on that criterion. As a contracting authority, make the comparability of tenders visible: state in the evaluation report which components you added for which bidder and at what price, and apply the same correction to all tenders. Set minimum requirements for free variants if you want to prevent a variant with less functionality or a shorter warranty from winning the comparison, and make clear whether a demonstration requirement is a condition of regularity, an evaluation element or merely informative.
Ask yourself
Does your lump-sum price really include everything needed to make the system work at the authority, or does your tender list indispensable components as options? Do you know that the authority may add an indispensable option to your lump sum without asking you first, where your tender itself states its price? Where in doubt about what belongs to the base contract, did you ask a question during the tender period? As a contracting authority: do your specifications impose minimum functional and warranty requirements on free variants, and is the role of any demonstration requirement clear? Does your evaluation report state the price corrections applied to each tender, so that comparability can be checked?
About this database
The Council of State (Raad van State / Conseil d'État) is Belgium's supreme administrative court. In disputes over public procurement — from contract awards to tenderer exclusions — the Council of State is the final arbiter. The rulings in this database are summarised by TenderWolf in plain language, with practical lessons for tenderers and contracting authorities. View all rulings →