Open Standards Rise in Japan

Once again Japan stands out for technology leadership in Asia. Last week, the Ministry of Economy, Trade and Industry issued its official Interoperability Framework.

It makes open standards -- including the OpenDocument Format (ODF)-- a required element of its procurement rules for technology and e-government.

The main objective of Japan's open standards requirement for procurement: interoperability (both data and process compatibility) and optimizing the value of ICT investments.

The Framework emphasizes a few specific policy points:

* the need to guarantee long-term access and retention of public documents.

* a prohibition on specifying individual products in procurement to avoid lock-in and dependency on non-interoperable products.

* when procuring software, open source software should be considered.

* decisions on software procurement should exclude software from considered based upon its development model or license.

* Preferred data formats are XML-based formats supported by multiple products/vendors with a low degree of dependence upon any single platform or specific technology.

And lastly, at the moment Japan's new Interoperability Framework recognizes only one acceptable document format: OpenDocument Format (ODF).

Categories: openstandards, ODF, Japan

Open Source Samurai

Japan is planning to put Microsoft to the sword. The government has announced that open source software will be top priority in public procurement, and vendors are lining up to provide it.

Open source may prove to be Japan's Field of Dreams, demonstrating to the world that when creating a market for open source, if government buys it, they will come.

The Ministry of Communications has issued new procurement guidelines that makes open source (specifically, Linux) a priority beginning on July 1.

Japan's open source move follows a recent policy declaring that technologies based upon open standards, including the OpenDocument Format (ODF), will have priority.

It is notable that the initial list of vendors jumping at the open source opportunities on offer by the Japanese government do not include any "pure" open source companies.

The Japanese government will need to be mindful that procurements involving open source are not like other IT procurements. They require real work by an agency to identify potential open source solutions and the support (internally, or by vendors, consultants or communities) BEFORE a tender is put into the market.


Categories: opensource, Japan

Technology Neutral ≠ Open Source Inaction

Memo to governments: technology-neutral policies on procurement do not mean that governments should do nothing about open source. While governments like Malaysia are neutralizing formal preferences (or mandates) for open source, they should not become passive about procurement or competition within the ICT market.

Technology neutrality is not a natural state, for governments or anyone else. People have preferences, even if policies on paper do not. Removing a sentence from an Open Source Master Plan, as Malaysia has done, does not magically level the playing field in ICT procurement. Neither does an open source preference for that matter. Procurement trumps policy every time.

To establish a truly neutral and competitive procurement environment, governments need to focus on 2 things: (1) setting clear objectives; and (2) burning your old, standard RFPs.

For step 1, Malaysia has it right. Its OSS Framwork sets the right targets: increase software choices and interoperability, reduce total costs of ownership and vendor lock-in, and ensure security.

Step 2 -- changing how procurement is actually done -- is much harder. It requires both changing rules and how people act. Tweaking your procurement policies will not work because you cannot "tweak" people's behavior. More dramatic action is needed.

Three actions can help drive changes in procurement practices and behavior. First, issue new standard RFP provisions that show agencies what neutral language looks like. Second, establish new criteria for bid evaluation that takes proper account of how open source works in the market. Lastly, find a way to make agency interactions with vendors more transparent. Too often, procurement decisions are made behind closed doors before an RFP is even issued. That is not a formula for value for money.

Categories: open, source, procurement, Malaysia, government

You Want Open ICT? Burn The Boats (or RFPs)

When it comes to technology policies, governments should heed the words of Hernan Cortez … “Burn the boats.” Or, more specifically, burn the RFPs.

Procurement is the real measure of a government’s approach to technology. How “open” a government is toward ICT is not measured by whether or not it buys open source software, but how it procures technology. It's not what you buy, but how you buy it that counts most.

As governments are discovering – most recently in Australia and UK-- tweaking existing procurement policies to encourage more bidding by open source companies will not create more choices, even when specific open source companies are pre-qualified.

Procurement band aids will not lead to increased competitive bidding, ICT choices and access to innovation. Your old procurement rules, evaluation criteria and standard RFPs will not work. They will not level the playing field. They will not break vendor lock-in.

Why? Because conventional government RFPs are structured for big, proprietary vendors. They evaluate bidding companies based on criteria inappropriate for open technologies.

For example, public agencies still focus more on purchasing products, while open source solutions are more about services and support. RFPs often under-value interoperability, and instead focus on system specs and large product suites. Criteria such as minimum annual revenues and established user base disadvantage small companies and tend to proliferate vendor lock-in.

And let’s be honest, too many RFPs are rigged, written in order to buy a specific solution from a specific company with whom the procurement officers have long-standing relationships. Their objective is not best value-for-money, competitive bidding or technology neutrality, but buying a specific system already pre-determined.

Government is Own Worst Enemy for Open ICT

Side note: Please take the poll over here!!! -------------->

At last week's GOSCON conference, Andy Stein, CIO for the City of Newport News, Virginia, hightlighted the fact that governments are often their own worst enemies when it comes to openizing their ICT ecosysems.

The traditional procurement system does not work when it comes to open source. Even worse, it prevents innovative public - private technology partnerships and even agency-to-agency collaboration. Policies on open standards, open source and open ICT that are not directly incorporated into procurement rules and practices are destined to fail.

These are points that I make in every conference at which I speak about open technologies. It is also emphasized in the Open ePolicy Group's Roadmap for Open ICT Ecosystems. Governments that want to "openize" their ICT ecosystems and drive innovation need to re-write their procurement rules.

This requires not only ending the practice of naming specific products, vendors and technologies in RFPs. The whole RFP process needs to be altered, or scrapped entirely. Criteria for selection of bids needs to change. Due diligance and contract management need to account for the fact that open source licenses, communities and companies work differently than proprietary vendors.

News Item of Note: Loss of Data by U.S. Agencies is Widespread.