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, June 11, 2010

Proprietary products vs competition

Proprietary products, by their nature, can lead to monopolized purchasing, which is obviously the antithesis of competition. They don't have to do so, however, when properly managed.

First, it must be remembered that proprietary products may compete against other products in a given market, in which case the proprietary product may be a distinguishing factor but not necessarily an essential feature of a product.

Automobiles, for instance, are distinguished by their proprietary designs, but that is not the essential feature governments look for when purchasing them. In cases like this, proprietary features should not be considered as a factor in product/service selection.

In other cases a proprietary feature may be embedded in a product to perform a functional task. If the task it performs does not significantly affect the functionality of the product, again, it should not be considered as an essential specification.

Other proprietary products can effectively monopolize a market, to some degree or other. In that case, much closer scrutiny of the truly essential features of a government's need must be articulated to encourage the entrance of competitive forces. Sometimes, the monopolizer must be taken head on, as the following story about IT technology illustrates.

EU Commissioner Warns IT Buyers Against Vendor Lock-in

European Commissioner Neelie Kroes warned governments and businesses to avoid vendors that try to lock them in with proprietary technology.

"Public and private procurers of technology should be smart and build their systems as much as possible on standards that everybody can use and implement without constraints," she said, adding that this is good for the bottom line because it promotes competition between suppliers and prevents vendor lock-in.

She asked vendors to act now to make their products interoperable with those of their competitors, and not to wait for a court to force them.

Now European Commissioner for the Digital Agenda, in her previous role as Competition Commissioner Kroes won a long antitrust battle against Microsoft over its failure to help competitors develop software that could interoperate with its Windows server products.

However, Kroes said, "Complex antitrust investigations followed by court proceedings are perhaps not the only way to increase interoperability."

Instead, the Commission is looking for other ways of making it more profitable for companies to license the information their competitors need to make interoperable systems, and less profitable to withhold that information.

"Any such initiative would probably be limited to certain types of IT products. And it would likely involve some form of pricing constraints," she said.

The European Interoperability Framework V.2 builds on an earlier set of rules and guidelines for cost-effective public sector procurement of IT systems. Kroes hopes that it will help public authorities avoid the dangers of long-term lock-in.

"It would also ensure competition between suppliers for follow-up contracts and for services. Governments should still be able to choose closed, proprietary products, she said, "but on the basis of a clear justification, rather than because it was the easy option."

By making it easier for industry groups to have their standards recognized, she said, "We want to make standard-setting more efficient, not more burdensome.'

Kroes also promised to help government IT buyers identify their real needs, so that they can specify products without reference to particular brands or suppliers.

"The skills of public authorities vary greatly when it comes to this aspect of procurement," she said. "Many authorities have found themselves unintentionally locked into proprietary technology for decades. [...] This is a waste of public money that most public bodies can no longer afford."

That waste can also directly affect businesses and citizens when public authorities' decisions force them to buy specific products to access a public service, rather than any product compliant with an applicable standard, she said. Examples include schools insisting on the use of a specific word processing system, or tax departments' online forms requiring a specific Web browser.

No comments: