Checklist for Procurement of Open Source Software in Switzerland presented – Pro-Linux

Community :: Politics / Law

The Swiss computer science conference (SIK) has submitted

a 15-point list that the IT Procurement of the Confederates should assist in the lawful acquisition of open source software.

Mirko Lindner

The Swiss checklist (PDF) consists of 15 questions with corresponding explanations, to assist the cantonal administrations in the preparation of a tender in ICT helpful. First, the first item on the list deals with the differences in the IT procurement between the business models with proprietary software and open source software. With proprietary software licenses are purchased, while it comes to services and support for open source software. Furthermore, it is clarified that in the event that no services around the free software needed, the procurement without a public tender may be carried out.

With OSS Directory and AlternativeTo two directories are presented which allow research on what Open- source solutions are available for which application. It should be noted that in general, the scope of the acquired software is too large, it is therefore money spent on services that are not needed. Here is an attempt also involving open solutions to procure only the realistic needs.

Often, the creator of the list is already in the procurement documents Competition hampered if there certain proprietary products are laid down. The SIK it looks in certain, well justified cases, however, not as problematic when an invitation to a particular publicly available open source solution is limited, since any company can offer their services, and thus does not impede competition, but encouraged the contrary will. In addition, it is recommended to explicitly mention in the announcement that open source software can be offered.

To encourage tenders from the open-source environment, recommends the SIK to consider some points. So contractors or consortia should be allowed so that several independent developers to join together on a project. In addition to be placed on the company size and number of employees, because the mostly small open source vendors exclude from the outset in the selection criteria not unnecessarily high demands. In the end is usually also responsible for only one department with a project in the proprietary environment of large companies.

As a lawful and permitted it refers to the SIK, positive characteristics of open source software in the technical specifications (TS) pretend or as an award criterion (CCC) highlight. So positive characteristics of open source, such as the use is not associated with additional costs on many jobs and the openness of the source code could be mentioned as ZK or even use properties are predefined under an open source license as TS.

Also important, the cost of an open source solution as Total Cost of Ownership (TCO) should be portrayed as open source is often more expensive to start and transition phase than proprietary solutions, but later this more than amortisiere itself. One argument for free software is also that in case of bankruptcy of the manufacturer’s software as open source, continue to remain usable, whereas proprietary software source code flows in the bankruptcy estate.

Open Source is one hand it to eighth, that sufficient service are available for an open solution, while also a consideration should be given to the strength and activity of the respective community. This is understandable on platforms such OpenHub. The research center for digital sustainability of the University of Berne has found in a study (PDF) related to the federal IT procurement system that here 43 percent of all ICT contracts are concluded without a public tender, while there are only 15 percent on average.