Thought you'd heard all the obstacles preventing Bristol City Council implementing an IT strategy based on open source and open standards? Now you can hear about one more.
To recap: big software companies use proprietary standards to sit on the market like the dragon Smaug on his mound of gold. Bristol's famed community of digital businesses are like aw-bless little hobbits. The council's IT strategy, like the government's, was going to cast open source and open standards like a magic spell that would slay Smaug and scatter his ill-gotten treasure among the jubilant halflings.
Only the spell doesn't have any power. It's not been cast with enough conviction.
What's worse is EU procurement rules are stacked against the hobbits. That's right: procurement rules, for which there aren't any suitable parallels in J.R.R.Tolkien's fantasy world. (Though if there were, they'd have been delivered by an edict of Elrond's tedious council).
And so to the point. Bristol wanted to procure services from local IT firms instead of ugly great multinationals. But procurement law prohibits such favouritism. So Bristol considered how it might get around the rules.
A free market fundamentalist would call foul on such shenanigans. But the Smaugs in this tale get favouritism under the procurement rules. Why shouldn't Bristol's hobbits?
Take Microsoft for example. EU procurement rules prohibit tenders for software from Microsoft. But they permit tenders that specify Microsoft software. This is clearly perverse. The whole point of procurement law is to ensure tenders aren't fixed. That should mean you can't specify what the product is, only the sort of product you want. But it doesn't.
The European Commission itself is the ideal case study in how these perverse rules work. In 2007 the Commission signed a €48m contract to update the Microsoft software on 36,000 PCs. The Commission tendered specifically for Microsoft software, precluding competition from competing software publishers.
The Commission told outraged MEPs it's tender could specify Microsoft as long as it was not asking to be supplied by Microsoft directly but by an accredited Microsoft dealer. There would be competition for its software contract, it said, between Microsoft dealers. That's like saying you have democracy when only rich white men have the vote.
Competition for software is stifled under this arrangement. Microsoft's ball-breaking grip on the market was sustained by rules overseen and payments made by the very institutions that were simultaneously fining it for operating a monopoly.
The EC's Microsoft-favouring software contract came into force on 1 March 2008, three days after it fined the software Smaug £680m for ignoring previous fines for abusing its monopoly power.
Lawyers told Bristol it couldn't specify Microsoft in its upcoming tender for software to put on its 7,000 PCs, even though the monopolistic market left it no choice but to use Microsoft software.
Mark Wright, the Bristol councillor campaigning to free the market from beneath Microsoft's fat belly, has been told he has to refer to the tender in council meetings as one for "Microsoft Windows or an equivalent alternative".
"It's nuts," he says. "There is no alternative."
Neither can Bristol issue tenders specifying software made by local firms. It would break those bizarre European rules. Wright says the council could get round the problem by breaking its contracts up. If they were small enough, only local firms would bid for them.
The council is finding, however, that since so few dominant software companies use proprietary standards, it can't easily break its IT systems and services down into modular components amenable to local firms. That's because the dragon's not yet been slain.
Simply some articles of interest and comments posted by the author of the Guam Procurement Process Primer, to add a broader context to the Guam procurement law issues discussed in the Primer. This Blog is intended for educational purposes. Nothing posted, said or implied or linked to in this blog, including any public comment, is intended to be taken as fact nor relied upon or used as legal advice. A quick guide to topics is available from the following Labels and Tags:
Labels and Tags
Accountability
(71)
Adequate documentation
(7)
ADR in procurement
(4)
Allocation of risks
(6)
Best interest of government
(11)
Best practices
(19)
Best value
(15)
Bidder prejudice
(11)
Blanket purchase agreement
(1)
Bridge contract
(2)
Bundling
(6)
Cancellation and rejection
(2)
Centralized procurement structure
(12)
Changes during bid process
(14)
Clarifications vs Discussions
(1)
Competence
(9)
Competition vs Efficiency
(29)
Competitive position
(3)
Compliance
(35)
Conflict of interest
(32)
Contract administration
(26)
Contract disputes
(4)
Contract extension or modification
(9)
Contract formation
(1)
Contract interpretation
(1)
Contract terms
(3)
Contract types
(6)
Contract vs solicitation dispute
(2)
Contractor responsibility
(20)
Conviction
(4)
Cooperative purchasing
(3)
Corrective action
(1)
Cost and pricing
(13)
Debarment
(4)
Determinations
(8)
Determining responsibility
(37)
Disclosure requirements
(7)
Discussions during solicitation
(10)
Disposal of surplus property
(3)
Effective enforcement requirement
(35)
Effective procurement management
(5)
Effective specifications
(36)
Emergency procurement
(14)
eProcurement
(5)
Equitable tolling
(2)
Evaluation of submissions
(22)
Fair and equitable treatment
(14)
Fair and reasonable value
(23)
Fiscal effect of procurement
(14)
Frivolous protest
(1)
Good governance
(12)
Governmental functions
(27)
Guam
(14)
Guam procurement law
(12)
Improper influence
(11)
Incumbency
(13)
Integrity of system
(31)
Interested party
(7)
Jurisdiction
(1)
Justification
(1)
Life-cycle cost
(1)
Limits of government contracting
(5)
Lore vs Law
(4)
market research
(7)
Materiality
(3)
Methods of source selection
(33)
Mistakes
(4)
Models of Procurement
(1)
Needs assessment
(11)
No harm no foul?
(8)
Offer & acceptance
(1)
Other procurement links
(14)
Outsourcing
(34)
Past performance
(12)
Planning policy
(34)
Politics of procurement
(52)
PPPs
(6)
Prequalification
(1)
Principle of competition
(95)
Principles of procurement
(25)
Private vs public contract
(17)
Procurement authority
(5)
Procurement controversies series
(79)
Procurement ethics
(19)
Procurement fraud
(31)
Procurement lifecycle
(9)
Procurement philosophy
(17)
Procurement procedures
(30)
Procurement reform
(63)
Procurement theory
(11)
Procurement workforce
(2)
Procurment philosophy
(6)
Professionalism
(17)
Protest - formality
(2)
Protest - timing
(12)
Protests - general
(37)
Purposes and policies of procurement
(11)
Recusal
(1)
Remedies
(17)
Requirement for new procurement
(4)
Resolution of protests
(4)
Responsiveness
(14)
Restrictive specifications
(5)
Review procedures
(13)
RFQ vs RFP
(1)
Scope of contract
(16)
Settlement
(2)
Social preference provisions
(60)
Sole source
(48)
Sovereign immunity
(3)
Staffing
(8)
Standard commercial products
(3)
Standards of review
(2)
Standing
(6)
Stays and injunctions
(6)
Structure of procurement
(1)
Substantiation
(9)
Surety
(1)
Suspension
(6)
The procurement record
(1)
The role of price
(10)
The subject matter of procurement
(23)
Trade agreements vs procurement
(1)
Training
(33)
Transparency
(63)
Uniformity
(6)
Unsolicited proposals
(3)
Friday, November 5, 2010
Bristling over closed-source market dominance
Procurement perversities stifle Bristol's IT
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment