Debate Details
- Date: 9 May 2016
- Parliament: 13
- Session: 1
- Sitting: 20
- Type of proceedings: Written Answers to Questions
- Topic: Cost of developing a new “next generation” ERP (Electronic Road Pricing) system
- Key themes/keywords: system, cost, generation, next, will, developing, winning, tenderer
What Was This Debate About?
This parliamentary record concerns written answers to questions in Parliament relating to the development and procurement of Singapore’s “next generation” Electronic Road Pricing (ERP) system. The specific exchange captured in the record focuses on (i) the cost of developing the new system, (ii) how that cost compares to other tender bids, and (iii) the Ministry’s approach to protecting privacy in relation to data collected by the system. The Minister responding—Mr Khaw Boon Wan—addressed questions about the tender award and the technical and governance aspects of the backend computer system that would be designed and built as part of the project.
Although the excerpt is brief, the legislative and administrative context is clear: ERP is a major public infrastructure and policy instrument used to manage traffic congestion and road usage. Upgrading to a new generation system involves not only engineering and procurement decisions, but also questions about data handling, anonymisation, and aggregation. In a written-answer format, Members of Parliament typically seek clarifications that can later inform public understanding, oversight, and—where relevant—future legislative or regulatory action. The record therefore matters as a window into how the Government justified cost, procurement outcomes, and privacy protections for a high-impact system.
What Were the Key Points Raised?
1) Tender cost and procurement comparison. One of the central issues raised was the cost of developing the new generation ERP system and how the awarded tender compared with competing bids. The record indicates that the “winning tenderer” was compared against the “next highest quote” of $1.2 billion. This comparison is significant because it speaks to procurement transparency and value-for-money considerations. In public procurement, the “winning tender” is not merely the lowest price; it typically reflects a combination of technical capability, delivery approach, risk allocation, and compliance with specifications. By asking for the comparison, the questioner sought to understand whether the awarded contract price was commercially justified relative to other bids.
2) Scope of work included in the tender. The Minister’s response, as reflected in the excerpt, indicates that the tender awarded for the next generation ERP system includes the cost of “designing and building the backend computer system” as well as “operating and …” (the excerpt truncates the remainder). This point matters because it clarifies what the quoted figure covers. For legal and policy research, the scope of “cost” is often contested: does it include only capital expenditure (design and build), or does it also include operational costs, maintenance, and lifecycle support? By specifying that backend design and build are included, the Government is effectively defining the cost baseline and preventing an overly narrow interpretation of the tender figure.
3) Data governance: anonymisation and aggregation. Another key issue raised was the Government’s approach to how data collected by the ERP system would be anonymised and aggregated to protect individuals’ privacy. This is a substantive policy and legal question. ERP systems necessarily involve the collection and processing of data to determine charges and manage road usage. However, the legal acceptability of such systems depends on whether personal data (or data that can identify individuals) is handled in a privacy-preserving manner. The question therefore targets the “how” of privacy protection: anonymisation (removing or irreversibly de-linking identifiers) and aggregation (using statistical or aggregated outputs rather than individual-level records).
4) Privacy protection as an operational requirement. The inclusion of privacy anonymisation and aggregation in the written exchange suggests that privacy is not treated as an afterthought but as an operational requirement embedded within system design and data processing workflows. For lawyers, this is important because it indicates that privacy safeguards may be implemented through technical architecture and data handling procedures, rather than only through post hoc compliance measures. It also signals that privacy considerations were sufficiently salient to be raised in Parliament in the context of procurement and system development.
What Was the Government's Position?
The Government’s position, as reflected in the Minister’s written answer, was that the tender awarded for the next generation ERP system includes the cost of designing and building the backend computer system, along with other components of the project (the excerpt indicates operational elements as well). The Government also addressed the cost question by referencing the comparison between the winning tenderer and the next highest quote of $1.2 billion, thereby situating the awarded price within the competitive tender landscape.
On privacy, the Government indicated its approach to anonymising and aggregating data collected by the ERP system to protect individuals’ privacy. In effect, the Government framed privacy protection as part of the system’s data processing design—an approach that would be relevant to how the system complies with applicable privacy expectations and governance requirements.
Why Are These Proceedings Important for Legal Research?
First, written parliamentary answers are often used by courts and practitioners as evidence of legislative intent or administrative understanding, particularly where the question concerns the interpretation of statutory concepts or the implementation of policy measures. While this record is not a debate on a Bill, it still provides contemporaneous insight into how the Government understood the scope, cost components, and privacy safeguards of a major public system. Such material can be relevant when interpreting later regulations, procurement-related contractual terms, or privacy-related obligations that arise from the system’s operation.
Second, the record is useful for legal research on privacy-by-design and the practical meaning of anonymisation and aggregation. Lawyers researching data protection issues may look for parliamentary statements that clarify what the Government considers sufficient privacy protection in operational systems. The explicit mention of anonymisation and aggregation helps establish that these are not merely aspirational principles but are treated as concrete mechanisms for protecting individuals’ privacy in the ERP context.
Third, the procurement and cost comparison element provides a basis for understanding how the Government justifies public expenditure and evaluates tender outcomes. In disputes—whether administrative, contractual, or policy-related—parties may need to show what was considered in the procurement process and what the Government regarded as the relevant cost components. Parliamentary answers that delineate what is included in the tender (e.g., backend design and build, and operational elements) can assist in construing the meaning of cost figures and the intended scope of deliverables.
Source Documents
This article summarises parliamentary proceedings for legal research and educational purposes. It does not constitute an official record.