Guidelines on OSS in Public Procurement

Transcription

1 Guidelines n Open Surce Sftware in Public Prcurement 01. Scpe and Applicability These guidelines apply t the public sectr in the prcurement prcess, including the stages f cntracting and cntract management. The guidelines address specifically the prcurement f Open Surce Sftware and cmpare the same with the prcurement f Prprietary Sftware. 02. Purpse The aim this dcument is t facilitate the identificatin f tender requirements and the crrespnding evaluatin methd f pen surce sftware. It als addresses legal issues related t Open Surce Sftware with reference t cntractual prvisins and a gvernance framewrk fr the management f the related licences at cntract management stage. 03. Use f the Guidelines This dcument is intended t guide Cntracting Authrities in assessing Open Surce Sftware and Prprietary Sftware in the prcurement prcess. It is nt t be interpreted as a mandatry r exhaustive guide t take int accunt in the prcurement prcess. Cntracting Authrities are expected t review the validity r therwise f these guidelines in each prcurement prcess. This dcument is nt t be cnstrued as legal advice. 04. Definitins Business Requirement Cntracting Authrity Functinal Requirement Generic Sftware Security Classificatin: Means the requirement f the Cntracting Authrity t have rights t use the sftware being prcured fr a particular purpse including but nt limited t redistributin and carrying ut mdificatins t the sftware. Shall have the same meaning as assigned in Public Prcurement Legislatin. Means the requirement f the Cntracting Authrity defining a particular functin f sftware r part f the sftware t accmplish an expected result. It cvers input, behaviur, prcessing and utput but excludes features r characteristics f the sftware including but nt limited t security, scalability, reliability which d nt dente a particular functin f the sftware. Als referred t as ff-the-shelf, means ready-made sftware. ICT Infrmatin and Cmmunicatin Technlgies. Intellectual Prperty Rights r Includes, withut limitatin, patents, trade marks, registered designs, IPR cpyright, design rights and any ther intellectual r industrial prperty rights. Invitatin t Tender Means the dcument issued r t be issued by a Cntracting Authrity inviting the public t submit prpsals fr the prvisin f wrks, supplies and/r services. Open Surce Sftware r OSS Means sftware fr which the underlying prgramming cde is available t users t read, make changes t it, and build new versins f the sftware incrprating their changes. In additin t access t the surce cde, the Open Surce Initiative (OSI) refers t ten (10) criteria that define Open Surce Sftware available at the OSI web site: Open Surce Sftware Licence Includes any such licence listed at Unclassified 1 f 11

2 Open Specificatins (infrmally referred t as Open Standards) Prprietary Sftware Prprietary Sftware Licence Public Prcurement Legislatin Technical Requirement Tenderer as an Open Surce Sftware Licence. Are frmalised specificatins which within the cntext f public services delivery, are characterised by the fllwing features: All stakehlders have the same pssibility f cntributing t the develpment f the specificatin and public review is part f the decisin-making prcess; The specificatin is available fr everybdy t study; Intellectual prperty rights related t the specificatin are licensed n fair, reasnable and nn-discriminatry (FRAND) terms r n a ryalty-free basis in a way that allws implementatin in bth Prprietary and Open Surce Sftware. Als referred t as clsed surce, means sftware which is nt OSS, cpyrighted and traditinally gverned by extensive terms and cnditins. Includes licences referring t: (i) (ii) (iii) (iv) (v) Prhibitins fr mdificatin t the riginal versin f the sftware; Prhibitins n redistributin f the riginal and/r any mdified versins f the sftware; A fee fr use; Restrictins n use e.g. restricted t nn-cmmercial use ; Prhibitins r limitatins n assignment and transfer. Means the Public Prcurement Regulatins (prmulgated by virtue f Legal Ntice 296 f 2010). Means the requirement f the Cntracting Authrity fr the sftware t be capable f particular attributes including but nt limited t mdificatins in rder t wrk with ther sftware. The persn submitting a respnse t the Invitatin t Tender. 05. Overview This dcument identifies varius stages in the prcurement prcess and addresses the issues that need t be cnsidered by Cntracting Authrities in relatin t Open Surce Sftware. The stages referred t are 1. Preparatin f a Business Case and Research, 2. Deciding n the Surcing Strategy, 3. Drafting Tender Requirements, 4. Evaluating Open Surce Sftware and Prprietary Sftware, and 5. Cntractual Cnsideratins, including cntract/licence management. 06. Preparatin f Business Case and Research There are different drivers which create a business need fr change. The drivers and the crrespnding business needs need t be dcumented within a cmprehensive business case. In additin, a prper research exercise shuld enable the identificatin f pprtunities fr Capitalising n existing investment, Future re-use pprtunities, Need fr surce cde access, Interperability pprtunities, Adpted and new standards, Innvative technlgies, Market cnditins and A cst estimate f direct and indirect csts as may be required t calculate the ttal cst f wnership (TCO). 2 f 11

3 Apprpriate research and/r cnsultancy als facilitate the prcurement prcess, aiding Cntracting Authrities t define accurate business requirements. The utcme f the research shuld be dcumented and attached t the business case as it may be required t justify related business requirements. 07. Deciding n the Surcing Strategy Open Surce Sftware can be acquired by Cntracting Authrities internally, free f charge and withut entering int a cntract, by dwnlading the sftware frm nline frges and repsitries. Hwever, the Cntracting Authrity needs t determine the suitability f the sftware against its requirements. In additin, if the Cntracting Authrity des nt intend t use the sftware as is, it needs t have the internal capability and resurces t perfrm related services [such the carrying ut f mdificatins] itself. If such capability and resurces are absent it may pt prcuring such related services separately. Where Cntracting Authrities pt t prcure sftware, requirements need t be identified fr Tenderers t prpse sftware (whether Open Surce r Prprietary Sftware) t meet the requirements. Cntracting Authrities may include sftware and related services in the same prcurement prcess. 08. Drafting Tender Requirements Once a decisin is taken by the Cntracting Authrity t prcure sftware frm the pen market, the Cntracting Authrity needs t cnsider Open Surce Sftware alngside Prprietary Sftware. As stated in the Gvernment f Malta Open Surce Plicy and Directive (GMICT P 0097 and GMICT D 0097), Cntracting Authrities must ensure a level playing field between Open Surce Sftware and Prprietary Sftware. Cntracting Authrities cannt refer directly t Open Surce Sftware as a requirement in the Invitatin t Tender. Open Surce Sftware (as with Prprietary Sftware) can nly be cnsidered in the prcurement prcess if it meets the business needs. Business needs are transpsed in the Invitatin t Tender thrugh Business, Technical and Functinal Requirements which may indirectly call upn the prperties inherent in Open Surce Sftware. What are the prperties f Open Surce Sftware and hw can a Requirement indirectly call upn such prperties? When a Cntracting Authrity assesses the technical and functinal specificatins f Open Surce Sftware and Prprietary Sftware, bth types f sftware are evaluated n a par level. There are n Technical and/r Functinal Requirements that can specifically distinguish between Open Surce and Prprietary Sftware. Business Requirements are what can distinguish between the tw. In fact, when a Cntracting Authrity assesses the license terms and cnditins f Open Surce Sftware and Prprietary Sftware, a Cntracting Authrity may nte that the Open Surce Sftware licence gives mre flexibility in the use f the sftware. The flexibility f Open Surce Sftware licenses is inherent in the prperties listed by Open Surce Initiative (OSI) in the Open Surce Definitin (OSD): 3 f 11

4 The Open Surce Definitin Intrductin Open surce desn't just mean access t the surce cde. The distributin terms f pensurce sftware must cmply with the fllwing criteria: 1. Free Redistributin The license shall nt restrict any party frm selling r giving away the sftware as a cmpnent f an aggregate sftware distributin cntaining prgrams frm several different surces. The license shall nt require a ryalty r ther fee fr such sale. 2. Surce Cde The prgram must include surce cde, and must allw distributin in surce cde as well as cmpiled frm. Where sme frm f a prduct is nt distributed with surce cde, there must be a well-publicized means f btaining the surce cde fr n mre than a reasnable reprductin cst preferably, dwnlading via the Internet withut charge. The surce cde must be the preferred frm in which a prgrammer wuld mdify the prgram. Deliberately bfuscated surce cde is nt allwed. Intermediate frms such as the utput f a preprcessr r translatr are nt allwed. 3. Derived Wrks The license must allw mdificatins and derived wrks, and must allw them t be distributed under the same terms as the license f the riginal sftware. 4. Integrity f The Authr's Surce Cde The license may restrict surce-cde frm being distributed in mdified frm nly if the license allws the distributin f "patch files" with the surce cde fr the purpse f mdifying the prgram at build time. The license must explicitly permit distributin f sftware built frm mdified surce cde. The license may require derived wrks t carry a different name r versin number frm the riginal sftware. 5. N Discriminatin Against Persns r Grups The license must nt discriminate against any persn r grup f persns. 6. N Discriminatin Against Fields f Endeavr The license must nt restrict anyne frm making use f the prgram in a specific field f endeavr. Fr example, it may nt restrict the prgram frm being used in a business, r frm being used fr genetic research. 7. Distributin f License The rights attached t the prgram must apply t all t whm the prgram is redistributed withut the need fr executin f an additinal license by thse parties. 8. License Must Nt Be Specific t a Prduct The rights attached t the prgram must nt depend n the prgram's being part f a particular sftware distributin. If the prgram is extracted frm that distributin and used r distributed within the terms f the prgram's license, all parties t whm the prgram is redistributed shuld have the same rights as thse that are granted in cnjunctin with the riginal sftware distributin. 9. License Must Nt Restrict Other Sftware The license must nt place restrictins n ther sftware that is distributed alng with the licensed sftware. Fr example, the license must nt insist that all ther prgrams distributed n the same medium must be pen-surce sftware. 10. License Must Be Technlgy-Neutral N prvisin f the license may be predicated n any individual technlgy r style f interface. 4 f 11

5 All ten criteria apply t Open Surce Sftware. Terms f licences that d nt prvide all such ten criteria wuld refer t Prprietary Sftware. Prprietary Sftware may, hwever, prvide fr sme (but nt all) f the criteria. Therefre, fr instance, in the case f Generic Sftware having ptential fr reuse, a Cntracting Authrity may request the right t re-use the sftware being prcured in subsequent prjects within the Gvernment f Malta withut limitatin as a Business Requirement. On the ne hand, the licensr f Prprietary Sftware may cmmit itself t allw such right f re-use withut limitatin. On the ther hand, Open Surce Sftware licences are a priri (by default) cmpliant with a request fr re-use withut limitatin. The re-use requirement is ne example whereby a Business Requirement calls upn the prperties f Open Surce Sftware. Other examples are listed in the Guideline n Public Prcurement f Open Surce Sftware issued by IDABC in May 2010 as fllws: The sftware may be used fr any purpse as the public agency des nt want t be restricted in hw it can use (r allw thers t use) the sftware. The public agency r a third party f its chice may study the surce cde as the public agency wants t be sure f the functining f the sftware; alternatively, the public agency may require that any member f the public can study the surce cde, in rder t prmte transparency f gvernment prcesses, r enable ther parties t prvide supprt and training assciated with the sftware. The public agency r a third party f its chice may mdify the sftware as the public agency des nt wish t be dependent n the riginal vendr fr bug-fixes, adaptatins and ther mdificatins The public agency can distribute the sftware, with surce cde and mdificatins, t anyne f its chice and prvide recipients with the same abilities t use, study, mdify and redistribute because the public agency needs t ensure that citizens and firms and ther agencies that access its services using the sftware r variants f the sftware d nt need t becme custmers f the riginal vendr in rder t d s; fr example, a natinal administratin may wish t be able t pass n the sftware, withut extra csts, t ther administratins at the lcal, reginal, natinal r Eurpean levels. The Business Requirements define the rights f use that the Cntracting Authrity wishes t prcure. Althugh all f the Business Requirements listed abve (cllectively), indirectly, refer t Open Surce Sftware, certain rights f use inherent in the same Business Requirements can be prvided by Prprietary Sftware. Hence, the requirement in Public Prcurement Legislatin nt t refer directly t a specific categry f sftware (such as Open Surce) because if a Cntracting Authrity requires nly a number (but nt all) f the Business Requirements, Prprietary Sftware may cmpete with Open Surce Sftware Cmparing Open Surce Sftware and Prprietary Sftware: The belw table summarises the salient features f Open Surce Sftware and Prprietary Sftware with a view t pint ut differences and similarities. The table is based n A Guide t Open Surce Sftware fr Australian Gvernment Agencies published by the Australian Gvernment Infrmatin Management Unit. Surce Cde Capital Expenditure Open Surce Sftware Surce cde is made available fr anyne free f charge t view, vet and mdify. Surce cde and bject cde available free ff charge. Prpnent may charge slely fr the medium in which the surce cde and/r bject cde. Prprietary Sftware Csts and ther restrictins may be impsed t prvide access t view the surce cde. Surce cde and bject cde are usually chargeable in additin t the related services. Related services such as custmisatin (sftware develpment), 5 f 11

6 cnfiguratin, integratin, implementatin, training, translatin may be chargeable. Maintenance and supprt are als chargeable (whether a supplier is engaged r internally if resurces are allcated) Custmisatin TCO csts need t be cnsidered including but nt limited t the underlying infrastructure. Custmisatin may be carried ut inhuse r utsurced t a supplier. Custmisatin is usually carried ut by the supplier f the sftware. Supprt In case f restrictive licences, 1 custmisatins must be made available if the sftware is redistributed. Usually develped in cmmunities that may be able t prvide prfessinal supprt in case f prblems with the sftware. Prfessinal supprt varies frm ne cmmunity t anther. As an indicatr: An pen surce sftware cmmunity with an active and diverse membership, a brad user base, a gd gvernance structure and regular updates is likely t be mre respnsive t user requests. 2 IPR fr custmisatins is usually kept by supplier f the sftware. Supplier f the sftware shuld prvide infrmatin n the manufacturer f the sftware, sftware life-cycles, gvernance prcedures and prduct radmaps. Innvatin Supprt may be prvided by the supplier f the sftware. Varius surces available within the cmmunity t cntribute t the creatin f the sftware which encurages innvatin. Innvatin is driven by the manufacturer that creates the sftware. Intellectual Prperty IPR is usually nn-negtiable. IPR can be negtiated. Re-Use Opprtunity Prmtes Re-Use. Re-distributin f mdificatins may be impsed in the case f restrictive licences. In such cases the gvernance aspect is critical. 3 Re-use is generally limited. Any requirement fr re-use needs t be specifically negtiated. Standards Generally adheres t Open Specificatins. In cases where Open Specificatins are nt adhered t, Open Surce Sftware may be custmised t adhere t Open Nwadays, manufacturers are generally aware f Open Specificatins. In cases where Open Specificatins are nt adhered t, the manufacturer must be requested t custmise the sftware t adhere 1 Fr an explanatin f restrictive Open Surce Licences see Sectin n Intellectual Prperty Rights. 2 Australian Gvernment Infrmatin Management Unit, A Guide t Open Surce Sftware fr Australian Gvernment Agencies, June2011, p Fr an explanatin n gvernance in relatin t Open Surce Sftware Licences see Sectin 10.2 n Cntract Management. 6 f 11

7 Specificatins. t Open Specificatins. Lck-in Release Management Restrictins n Use Bth Open Surce and Prprietary Sftware may drive Cntracting Authrities t be lcked-in. Lck-in is dependant mainly, but nt limitedly, t lack f adherence t Open Specificatins and lack f supprt ptins. Sftware patches, sftware updates and prduct releases shuld be aligned with Gvernment gvernance prcess, including evaluatin prcesses, testing prcedures, patch management and technlgy life cycle. If the sftware is used as is, generally, n restrictins apply. In case f distributin, bligatins are triggered n the distributr including but nt limited t an bligatin prvide access t the surce cde under the terms and cnditins f the licence. Cnditins within licenses may restrict the use f the sftware including but nt limited t cnditins referring t hardware, site, user, frequency, dates and thers. These terms are, hwever, negtiable. Security Training In the case f mdificatins, Open Surce Sftware Licences that are restrictive require the user t make available mdificatins t the surce cde available in the case f distributin. All sftware may be vulnerable t attacks. Therefre security risks in relatin t the sftware need t be identified (by the Cntracting Authrity r thrugh advisries) and assessed (by the Cntracting Authrity). In additin, apprpriate patching and security prcedures need t be adpted t mitigate security risks. Requires Administrative and End User Training even if the upgrading frm ne versin f a slutin t anther. Liabilities and Warranties Generally, Open Surce Sftware Licences exclude liabilities and warranties t the maximum extent permitted by law. A Cntracting Authrity wuld need t prcure such liabilities and warranties frm a supplier at a cst. Liabilities and warranties are negtiable. 09. Evaluating Open Surce Sftware and Prprietary Sftware 09.1 Business, Technical and Functinal Requirements Bth Open Surce Sftware and Prprietary Sftware can be checked against the Business, Technical and Functinal Requirements. Where the Cntracting Authrity justifies the need f such requirements, the evaluatin entails merely an assessment n whether the sftware prpsed by the Tenderer meets the requirements set by the Cntracting Authrity in the Invitatin t Tender i.e. whether it meets minimum requirements. In such cases any difference between Open Surce Sftware and Prprietary Sftware may feature, financially, thrugh the Ttal Cst f Ownership. This apprach, hwever, assumes that a Cntracting Authrity is awarding a public cntract n the basis f the lwest price ffered cmpliant with the tender specificatins. In cases where the Cntracting 7 f 11

8 Authrity sets tender requirements that are desirable, the sftware prpsed by the Tenderer may be evaluated and the public cntract awarded n the basis f the mst ecnmically advantageus ffer Ttal Cst f Ownership: The ttal cst f wnership (TCO) is a term used t determine the ecnmic value f an investment. It is extensively used in prcurement t dente value fr mney. TCO includes direct and indirect csts. Direct csts are identifiable at the mment f acquisitin. They are fixed at the mment f acquisitin but variable in the lng run. Indirect csts are nt easily identified given that they refer t csts incurred by the Cntracting Authrity as a result f the acquisitin. Such csts are generally nt fixed and d nt relate specifically t the acquisitin (but varius acquisitin). Indirect csts may be gruped int a fixed cst, n the basis f estimates, t facilitate evaluatin. A list f examples f what cnstitutes direct and indirect csts is referred t belw. The list in nt exhaustive and there may be variances. Direct csts Sftware and Hardware Installatin; Systems Integratin and Data Migratin; Sftware Custmisatin; Sftware and Hardware Maintenance; Service Management; Training; Analysis and Research; and Warranties and Licenses. Indirect Csts Infrastructure Csts, including upgrade related t bandwidth requirements; Insurance Csts (Risk insurance against trademarks and patents infringements 4 ); Office Space; Pwer and cling; In-huse supprt (including develpers, e.g. t facilitate integratin, t accelerate timeframes, t cntribute back t cmmunity); Failure Expenses; Perfrmance Upgrades; Auditing; Exit Csts; and Re-tendering/Transitin csts/decmmissining Such csts may be incurred at acquisitin stage r, subsequently, during the term f the cntract (i.e. length f investment). Althugh incurred in different stages, the Cntracting Authrity needs t take int accunt all csts pssible at acquisitin stage, pssibly by limiting variables during the term f the cntract e.g. agreeing t fixed csts ver the term. 10. Cntractual Cnsideratins: 10.1 Cntractual Prvisins: The mre relevant cntractual cnsideratins in relatin t Open Surce Sftware cncern: Intellectual Prperty Rights Open Surce Sftware Licences grant the basic freedms t users t cpy, mdify and distribute the surce cde and bject cde. In the case f mdificatins, a number f Open Surce Licences require that the mdificatins t the sftware are made available t the develpment cmmunity under the same terms and cnditins f the riginal Open Surce Licence. These licences are referred t as restrictive licences because they impse an bligatin t allw cpies, mdificatins and distributin 4 Refer t: 8 f 11

9 t the derived wrk (i.e. the wrk prduced frm mdificatins t the Open Surce Sftware). Other Open Surce Licences are permissive, allwing the user t cmmercially explit the mdificatins under a Prprietary Sftware Licence. Hence, whereas restrictive Open Surce Licences cannt be cmbined with Prprietary Sftware Licences, permissive Open Surce Licences can be cmbined with Prprietary Sftware Licences. This implies that when a supplier prpses Open Surce Sftware regulated by a restrictive Open Surce Licence, the supplier must ensure that mdificatins r derivative wrks are capable f being distributed with and under the same terms and cnditins applicable t the Open Surce Sftware cmpnent. Likewise the cntract must treat Open Surce Sftware gverned by a restrictive Open Surce Sftware Licence separately by expressly stating the terms and cnditins f the applicable Open Surce Licence (which is restrictive) in a separate schedule f the cntract. In case f permissive Open Surce Sftware Licenses the mdificatins r derived wrks can be regulated by the standard terms and cnditins listed by the Cntracting Authrity in the cntract t regulate the wnership (including assignment) f Intellectual Prperty Rights created during the term f the cntract. Open Surce Sftware Licences generally exclude warranties and liabilities. Hwever, there is nthing prhibiting a supplier frm agreeing t prvide warranties ensuring that: 1. The Cntracting Authrities has the all the rights necessary t use the sftware as intended and n a perpetual basis. 2. The Cntracting Authrity is indemnified against breaches f third party Intellectual Prperty Rights in the curse f using the sftware prvided, cvering any lsses, damages, csts r expenses r ther liabilities incurred. When prcuring Open Surce Sftware, Cntracting Authrities need t set a time-frame within which the supplier is t prvide a cpy f r access t the surce cde n delivery f the Open Surce Sftware and any mdificatins r derived wrks, at n additinal cst. Escrw arrangements are nt required in the case f Open Surce Sftware given that the surce cde and bject cde are freely available Due Diligence A supplier f Open Surce Sftware wuld be required t warrant that the prpsed sftware is cmpatible with any existing technlgies f the Cntracting Authrity. Due diligence bligatins n the supplier, ensure that the supplier prpses Open Surce Sftware that has been evaluated and tested against the ICT infrastructure f the Cntracting Authrity. Effectively, due diligence carries frward the prmises made at prcurement stage Service Imprvement An bligatin n the supplier t mnitr and cntribute t the develpments f the Open Surce Sftware prpsed ensures that the Cntracting Authrity benefits ff the mre recent versins r updates t the sftware. The cntract shuld cater fr a prcess agreed t by the parties n hw upgrades r updates shall be incrprated t prpsed Open Surce Sftware Maintenance and Supprt In absence f any express prvisin, Open Surce Sftware maintenance and supprt is dependent upn patches, updates and sftware prduct releases by the relevant Open Surce Sftware cmmunity. Therefre, in prcuring sftware and related services, the Cntracting Authrity has an interest t blige the supplier t warrant that it will maintain and supprt the sftware thrughut the cntract term, irrespective f the existence f the cmmunity. 9 f 11

10 10.2 Cntract Management This sectin prpses a gvernance framewrk specifically fr dealing with Open Surce Sftware licences. It identifies the risks assciated with the use Open Surce Sftware Licences (nt Open Surce Sftware) and prpses mitigatin t the risks identified. This table is based n A Guide t Open Surce Sftware fr Australian Gvernment Agencies published by AGIMO in June Purpse fr which OSS is required Assciated Risk Risk Mitigatin Use as is (withut distributin r mdificatin) - Negligible - Read, understand and ensure cmpliance with all licence terms and cnditins. Use as is (with distributin but withut mdificatin) - Lack f distributin rights; - Obligatins triggered upn distributin; - Liability and warranty risks assumed as distributr f the sftware - Review licence t cnfirm distributin rights; - Read, understand and ensure cmpliance with all licence terms and cnditins, including bligatins triggered upn distributin. - Disclaim r ther limit liabilities and warranties as distributr f the sftware. Mdify - Lack f mdificatin rights; - Cnflict between arrangements made t carry ut mdificatins t the sftware, implement and maintain and supprt and the licence terms; - Lack f cmpatibility between sftware licences f different cmpnents e.g. between restrictive OSS licences and Prprietary Sftware licences. - Lack f clear understanding n the use f the sftware in case f distributin may trigger restrictive licence terms. - Review licence t cnfirm mdificatin rights; - Ensure that IPR f wrks is assigned t the Cntracting Authrity thrugh public cntract and cntracts f emplyment. - Determine the applicable licences prir t distributing the packaged sftware. - Ensure that the use f the sftware is determined prir t distributin in rder t identify the relevant bligatins f the licence terms and cnditins and cmply with the same. 11. Related Dcuments This dcument must be read in cnjunctin with the fllwing GMICT publicatins: Open Surce Sftware Plicy (GMICT P 0097) Open Surce Sftware Directive (GMICT D 0097) Open Standards Plicy (GMICT P 0099) Open Standards Directive (GMICT P 0099) 10 f 11

11 12. Resurces Australian Gvernment, Department f Finance and Deregulatin, Australian Gvernment Infrmatin Management (AGIMO), A Guide t Open Surce Sftware fr Australian Gvernment Agencies, June 2011, Versin 2.0 available at: IDABC, Eurpean egvernment Services, Guideline n Public Prcurement f Open Surce Sftware, March 2010 (revised June 2010) available at: 0Surce%20Sftware.pdf 11 f 11