When your own specifications say 'data collection is not an end in itself', your €2.5 million works contract turns into a services contract
The Council of State upholds the Walloon Region's tutelage decision annulling the City of Namur's award of a €2.57 million Intelligent Transport System — the 'works contract' classification fails even though works represent 83% of the budget, because the specifications themselves describe data collection as a mere means serving a mobility-management end.
What happened?
In late 2016 the City of Namur sets out to become a 'Smart City' and launches an Intelligent Transport System project (STI, FEDER project 'Namur Innovative City Lab'): ANPR cameras, sensors and variable message panels on the main approach roads, a web and mobile app, a dashboard for managers and citizens. Total budget around €2.57 million: €425,000 for software design and development, €830,000 for dynamic information panels at bus stops, €705,000 for fixed and mobile dynamic panels, €610,000 for data-collection devices. On 30 September 2016 the City voluntarily — without obligation — sends its draft specifications to the Walloon Region (tutelage authority) for advisory opinion. On 13 October the Region replies unambiguously: this is a services contract, not works, because the supply and installation of the collection devices 'are merely a means to achieve the principal and final aim, which would be to broadcast information to citizens in real time to influence their behaviour and to develop a mobility strategy on the basis of the collected data'. On 3 November the City replies briefly: no, we keep 'works', because the financial weight of works is greater. No further response from the Region. The City interprets that silence as agreement and adopts the specifications on 15 December 2016. Notice published in the Bulletin of Awards on 20 January 2017 and in the OJEU on 25 January 2017. Four bids submitted by 4 May 2017: Proximus-Genetec-BeMobile, Jacops, Macq-Fabricom, SPIE Belgium. On 29 June 2017 the Aldermen's College awards the contract to the temporary association Macq-Fabricom. The file is sent to the Region on 4 July for tutelage; deadline extended to 19 September. On 19 September 2017 the Region annuls both the 15 December 2016 deliberation (adopting the specifications) AND the 29 June 2017 award decision, because the 'works' classification breaches Article 3 of the Public Procurement Act of 15 June 2006. The City rushes to the Council of State on extreme urgency on two grounds: (1) the object of the contract and the financial weight of works (83.46% per the FEDER project sheet, 67-74% per the bidders' bills of quantities) require the 'works' classification; (2) legitimate expectation, because the Region's silence on the 3 November letter amounted to approval. The Council rejects both. On the qualification: the specifications themselves state in section I.1 that 'data collection is not an end in itself' — and list three components (collection, processing, broadcasting) of which only collection involves works. But within that component itself, the ancillary works (power, connections, placement) are accessory to the equipment supply, which is itself accessory to the design service. The technical selection criteria require a master in computer science with software architecture competencies and a telecommunications expert — not a works contractor. The award criteria evaluate the quality of the integrated system (45 points), a detailed strategy on one axis (30 points), additional IT services (5 points) and the relevance of equipment for conditional tranches (20 points) — the assessment focuses on technical quality and urban integration, not on works to be carried out. The 83/17 financial split is incomplete: it does not separate equipment (supplies) from works, and omits several services (maintenance, communication, design). The CPV codes argument is irrelevant — a wrong code can result from a wrong qualification. The comparison with a DGO2 contract for cameras on hydraulic installations is rejected: qualification is done in concreto. On legitimate expectation: the 13 October letter was clear; the City's 3 November letter contained 'formally no request asking the Region to confirm or deny its position', so silence could not be interpreted as agreement. Consequence: the City must restart the procedure ab initio (new specifications, new publication, new bids) — risk of losing FEDER subsidies, and the competitive advantage is gone because all bidders now know each other's offers via the reasoned award decision.
Why does this matter?
For contracting authorities launching 'Smart City', e-gov or IoT projects — counting cameras, urban sensors, dynamic panels, IT platforms coupled with physical devices — the qualification of the contract is not played out in financial volumes, but in the drafting of the specifications. Three concrete pitfalls emerge from this ruling. First: the introductory sentence explaining 'why' the contract is being launched can seal the qualification. If you write that cameras are there to 'broadcast information to citizens in real time' or to 'influence behaviour', you have yourself described the installation as a means — and thereby reclassified the matter as a service. Second: selection criteria betray the real nature of the contract. Asking for a master in computer science and a software architect means selecting a service provider, not a contractor. If you really want a works qualification, you need accreditation and contractor references. Third: the assumption that 'works share > 50% = works contract' is wrong. The Court of Justice and the Council of State assess the principal object in concreto — the amount is just one criterion among several. The ruling also confirms that the tutelage authority can annul an award even after four bids have been submitted and a winner designated, and that missed accreditation is the principal sanction: a contractor classified for works does not need accreditation for a services contract — so a wrong qualification may have excluded potential candidates who could have bid without accreditation. For bid managers: if you encounter a 'Smart City' specifications document classified as works but whose selection criteria require IT skills and whose evaluation focuses on the quality of a system, that is a grey zone that can sink the contract — check before bidding.
The lesson
If you launch a mixed contract combining physical equipment and an IT system (Smart City, surveillance, IoT platform, integrated ticketing), three things to do before adopting the specifications: (1) read your own project description — if you write that the equipment is there 'to' achieve a management or service goal, you have admitted yourself that the contract is a service, and the word 'works' on the cover will not save it; (2) look at your selection criteria — if you require software architects, masters in computer science or references in data integration, you are selecting a service provider, not a contractor; (3) the financial breakdown 'works versus services' is not a sufficient argument if it confuses equipment (supplies) with works, and if it omits maintenance, communication and design. If the qualification remains in doubt, request a formal opinion from the tutelage authority AND an explicit agreement — silence is never approval. And if the tutelage authority writes to you that it is a service, do not bet that it will not come back to it at the award stage: it can, and it will.
Ask yourself
Before adopting the specifications of a 'Smart City' or IoT contract you want to qualify as works: open the document and run three simple searches. (1) Does the word 'means' appear about the equipment, paired with a purpose (manage, broadcast, inform, process)? If yes, you have just written yourself that this is a service. (2) Do your technical selection criteria ask for a master in computer science, a software architect or references in integrated platform development? If yes, you are selecting a service provider. (3) Do your award criteria allocate more points to 'system quality', 'strategy' or 'data integration' than to works to be carried out? If yes, same answer. Three 'yes' = reclassify as services in the specifications, or expect annulment by the tutelage authority or the Council of State.
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 →