JHS 166 Terms and Conditions of Public IT Procurement

Annex 2. Special Terms and Conditions for the Procurement of Client’s Application under Open Source Software Terms (JIT 2015 – Client’s Applications Open Source)

  • Version: 2.1
  • Published: 25 June 2018
  • Valid until: until further notice

INSTRUCTIONS FOR USE

Special terms and conditions for the procurement of client's applications include the Special Terms and Conditions for the Procurement of Client’s Application under Open Source Software Terms (JIT 2015 – Client’s Applications Open Source), the Special Terms and Conditions for the Procurement of Client’s Application under Software Terms Other than Open Source (JIT 2015 – Client’s Applications Non-Open), and the Special Terms and Conditions for Projects Implemented Using Agile Methods (JIT 2015 – Agile Methods). Before any application procurement, the client must always select the most suitable special terms and conditions. In some cases, it may be appropriate to enable, in the invitation to tender, the submission of tenders based on different special terms and conditions.

In the special terms and conditions for the procurement of client's applications, “client's application” refers to a program or its part produced specifically for the client, and any expansions, modifications, additions (such as interfaces), configurations and parameterisations of standard software made by the supplier for the client. The delivery of the client's application may also include standard software if so expressly agreed in the agreement.

Under these terms and conditions, the client procures a client's application licensed under an open source software licence. The use of an open source licence offers advantages, particularly in the following situations:

  • When procuring an application for activities that are carried out in a similar or corresponding manner by several procurement units.
  • When procuring an application subject to special publicity or transparency requirements.
  • When procuring an application which is to be integrated with other systems, requiring cooperation between several parties. In such case, it should also be considered whether the supplier should be required to develop the application in public in the manner enabled by Section 15 of these terms and conditions in order to facilitate cooperation with other partners of the client.

When using the special terms and conditions for open source procurement, it may be necessary to consider in some situations whether parts of the client's application should be acquired under terms and conditions other than those of an open source code licence. Correspondingly, it may be necessary to indicate in the invitation to tender to what extent standard software, to which their own licence terms are applied, are permitted. Examples of special reasons for procuring the client's application under terms and conditions other than those of an open source licence include situations where it becomes apparent during the preparation phase of the procurement that reasonable offers cannot be obtained using an open source licence.

These Special Terms and Conditions must not be applied to those parts of a total delivery that have been indicated in the agreement to include software other than open source code software. Such parts must be itemised in the agreement and, accordingly, make a reference to the Special Terms and Conditions for the Procurement of Client’s Application under Software Terms Other than Open Source or, with regard to standard software, to the licence terms of the standard software.

These terms and conditions are suitable mainly to the procurement of a client's application following the so-called waterfall model. For the procurement of client’s applications using so-called agile methods, it is recommended that the JIT 2015 Special Terms and Conditions for Projects Implemented Using Agile Methods (JIT 2015 – Agile Methods) are used instead.

The client's application must fulfil the requirements set out in the agreement and the specifications concerning the implementation. The contracting parties should pay attention to ensuring that the specifications fulfil the requirements. If it becomes apparent in the specification phase that a requirement will not be fulfilled or that it will not be e.g. expedient to implement it, the supplier must notify the client of this and the matter must be handled through the change management procedure.

The client often procures the application so that it is built upon standard software which is parameterised or supplemented to meet the client's requirements. The object of delivery, which consists of the client's application and any standard software possibly included in the delivery, must be specified in the agreement. Attention should also be paid to the following:

  • The testing and acceptance procedures apply to the entire object of delivery, including any related standard software. The special terms and conditions for application procurement include stipulations on the testing and acceptance procedure. However, it may be necessary to agree upon the testing and acceptance process in more detail in the agreement. Documentation forms an essential part of the product or service. Therefore, the documentation needs to be inspected in connection with the testing, as well.
  • If the delivery includes standard software programs, they must be itemised in the agreement. Unless otherwise agreed, operating systems and database management programs may be standard software licenced under terms and conditions other than those of open source software; however, standard software must otherwise be licenced under the terms and conditions of open source software. Rights of use to standard software are primarily determined according to their own licence terms and conditions. The scope of the rights of use to standard software must correspond with the requirements presented by the client in its invitation to tender.
  • If the object of the agreement is software critical to the client, it is advisable to prepare for the end of software maintenance or any discontinuation of the operations of the software supplier. The source code and associated document material related to software important to the client may be stored in the possession of an independent provider of a source code storage service (escrow agent) by entering into a separate source code storage agreement. The provider of the source code storage service will store the material and, in case of problems, release the source code under the terms and conditions agreed in the storage agreement. It should be noted that the source code of third-party standard software cannot usually be obtained or stored even by escrow agents. In these situations, the source code can principally be stored only for that part of the solution the source code of which is held by the supplier and the source code of which it is entitled to transfer.

Software is developed in source code form and, for the purposes of code management, the source code is maintained in a version control system. The starting point of the terms and conditions is that the source code is released in a public version control system after development, but no later than within thirty (30) days of the acceptance of the delivery. The terms and conditions also provide for the use of a public version control system already at the beginning of the development work so that anyone can monitor the development process. This is advantageous if the project requires, e.g., cooperation between several suppliers, the customer or other parties.

There are a number of open source software licences. The definition of open source software and a list of associated licences are available at http://www.opensource.org/. The EUPL 1.1 licence is available at http://joinup.ec.europa.eu/software/page/eupl/licence-eupl. See also JHS 169 Use of open source software in public administration.

Primarily, there should be no restrictions for licences used so that as many different technologies as possible can be offered (or suitable components can be selected during the project). If the procurement unit has a justifiable reason to require a specific open source software licence from the supplier, the licence should be defined in the invitation to tender and a corresponding stipulation should be added to the agreement. Such a reason could, in certain situations, be the use of specific open source code software by the procurement unit, for example. Usually, compatible licences should also be permitted. In some cases, the client may want to use several licences in its relicensing, i.e. a dual licence.

In the application procurement phase, special attention must be paid to the prevention of vendor lock-in by preparing to withdraw from the use of the system during or at the end of the system life cycle and for the costs resulting from it. According to these terms and conditions, the supplier has the obligation to design the object of delivery so that data can be detached in a reasonable manner. Any costs arising from the withdrawal from the application should be taken into account in the offer comparison phase already when procuring the specific application.

For the procurement of a client's application, a procurement agreement must always be entered into. These Special Terms and Conditions are attached to the procurement agreement, together with JIT 2015 General Terms and Conditions. With regard to the order of interpretation, these Special Terms and Conditions take precedence over the General Terms and Conditions. Where deviations with respect to the special and general terms and conditions are necessary, provisions on such deviations should be included in the procurement agreement.

On the date of publication of this recommendation, the portal referred to in Section 14 (7) is avoindata.fi.

Requirements concerning the use of open interfaces should preferably be defined in the invitation to tender. Annex 10 of the recommendation JHS 166 offers supporting material for the use of open interfaces.

These use instructions do not form part of the agreement.

Agreement date and no.: _____________________________Annex no.: _____________

JIT 2015: Special Terms and Conditions for the Procurement of Client’s Application under Open Source Software Terms

    1 Scope of application

(1) These Special Terms and Conditions shall be applied to the client’s procurement of an application created based on an assignment by a public procurement unit and made for the client's needs and according to the client's requirements, if these Special Terms and Conditions have been referred to in the agreement and to the extent it has not been otherwise agreed in writing.

(2) These Special Terms and Conditions are used together with the General Terms and Conditions of Public IT Procurement. In case of any conflict, these Special Terms and Conditions take precedence over the aforementioned General Terms and Conditions of Government IT Procurement with regard to their corresponding provisions.

    2 Definitions

In addition to the following definitions of the Special Terms and Conditions, the definitions of JIT 2015 General Terms and Conditions shall be applied.

platform software

fialustaohjelmisto

generally available operating systems and database management software

application to be published

fijulkaistava sovellus

the software code included in the material to be delivered, and its documentation; however, not including client-specific software installation and definition data, nor platform software or its software code or documentation

public version control system

fijulkinen versionhallintajärjestelmä

a service open to the public where the software source code, together with other material associated with software development, can be maintained in an expedient manner for software development purposes

development environment

fikehitysympäristö

the technical platform required for the development of the client's application agreed in the agreement, such as hardware, software and data links, and the required licences and their maintenance

operating environment

fikäyttöympäristö

the technical platform (servers, system software, data links, etc.) on which the object of delivery is installed for testing or production use

handover

filuovuttaminen

the handover of the object of delivery to the client for acceptance testing.

A part of delivery can also be handed over for approval testing.

specifications

fimääritykset

the technical and functional properties of the client's application defined by the contracting parties for the object of delivery on the basis of the requirements, of which the client and supplier have agreed or will agree in writing

client's application

fitilaajan sovellus

software or a part thereof created for the client, expansions and additions (such as interfaces) to standard software made by the supplier for the client, configurations, parameterisations and any other possible software delivered by the supplier as part of rollout, apart from standard software

The client's application also includes its documentation.

material to be delivered

fitoimitettava aineisto

material to be delivered refers to the material, such as software code, documentation, configuration information, instructions and other material, which the supplier delivers to the client in order to fulfil the agreement.

With regard to software code, material to be delivered includes both the source code and the executable form of the code.

standard software

fivalmisohjelmisto

software or a part thereof developed and marketed by the supplier or a third party and defined as standard software in the agreement, together with its documentation

Standard software may be open source software. Standard software or its documentation is not the client's application.

error

fivirhe

the object of delivery does not fulfil the agreed requirements and specifications, or it does not function in accordance with them

compatible licence

fiyhteensopiva lisenssi

a licence, the terms and conditions of which are not in conflict with another open source software licence in a situation where the same entity is licensed at the same time under both another licence and the compatible licence or, if the method of combining different parts of the entity enables separate licensing terms for different parts, compatible licence refers to any open source software licence

    3 Delivery

(1) The client's application has been specified in the agreement. If the object of delivery includes standard software programs, such programs and the special terms and conditions governing them, if any, must be stated in the agreement.

(2) Unless otherwise agreed, the delivery includes the design, specification, implementation, testing and rollout of the client's application. In addition, the delivery may include other tasks, such as those associated with data conversion and personnel training, if they have been agreed upon in the agreement.

(3) Delivery phases, the delivery schedule and the resources required are agreed upon in the agreement.

(4) The support, maintenance and further development of the client's application are agreed separately.

    4 Testing and the acceptance of the delivery

(1) The supplier shall perform the supplier's tests agreed in the agreement for the object of delivery or its part before the supplier hands over the object of delivery or its part to the client for intermediate testing or acceptance testing. Unless otherwise agreed, the supplier shall perform the tests in accordance with its practices using the material supplied by the client in advance. The accepted performance of the supplier's testing is an absolute requirement for the supplier’s right to hand over the object of delivery or its part to the client for acceptance testing. The supplier's testing shall be deemed accepted when the tests performed by the supplier no longer reveal any errors which the client might, with justified cause, consider to prevent acceptance testing from being performed. The supplier shall notify the client of the time when the object of delivery or its part is ready for the client's acceptance testing and provide the client with an account of the testing performed and its results.

(2) The client shall, at its own expense, bring the operating environment required in testing into compliance with the agreement, unless otherwise agreed. The supplier shall hand over the object of delivery for acceptance testing so that it is installed in the operating environment in accordance with the agreement according to the delivery schedule. The supplier shall provide the client with operating instructions for the client's acceptance testing as well as the documentation concerning the object of delivery. The supplier shall also provide the client's representatives with agreed training for the performance of the tasks in question.

(3) The client shall perform the acceptance testing. The client shall provide an acceptance testing plan for the supplier in advance for commenting. However, the acceptance testing plan is not binding, and the client shall have the right, without being limited by the plan, to perform all tests it deems necessary. Unless otherwise agreed, the client shall have thirty (30) days to perform the client's acceptance testing, starting from the date on which the supplier has reported in writing that the object of delivery or its agreed part is ready for acceptance testing and has handed over the object of delivery for testing in accordance with Section 4(2). The supplier may not hand over the object of delivery or its part to the client for acceptance testing before the mutually agreed date, unless the client gives its express written consent to it. The contracting parties may agree that the supplier assists the client during acceptance testing.

(4) Unless otherwise agreed, the client shall test the agreed intermediate stages within seven (7) weekdays after the supplier has announced in writing that testing may be started. The acceptance of an intermediate stage does not release the supplier from liability concerning errors which are revealed during later testing stages and which could not be and cannot be reasonably expected to have been detected during testing at intermediate stages. The acceptance of an intermediate stage is a precondition for the commencement of the next stage, unless otherwise agreed.

(5) The supplier shall immediately correct any errors discovered during acceptance testing. The time reserved for acceptance testing shall be extended by the time the supplier needs to correct the error and the client reasonably needs for the testing and acceptance of the corrected errors. If an error is caused by standard software, the supplier shall correct the error or have the error corrected at its own expense and according to its possibilities. If this is not reasonably possible, the supplier shall work around the error at its own expense. If creating a workaround is not reasonably possible through generally available means, the parties may agree upon additional work to work around the error, or the client shall be entitled to a price reduction. If the error is so significant that, due to the error, the purpose of the agreement remains essentially unfulfilled, the client shall have the right to cancel the agreement, unless the error concerns the standard software required by the client.

(6) The client shall immediately notify the supplier in writing of any errors it has detected in the application; however, no later than within three (3) working days after the time reserved for the client's acceptance testing has ended.

(7) The object of delivery or its part shall be deemed accepted if the client has not given any notification of errors within the time stated in Section 4(6) or if the client takes the object of delivery or its part into production use.

(8) Acceptance will not be prevented by minor errors that do not prevent the object of delivery from being used in the agreed purpose of use or prevent its operation. However, the supplier is obligated to correct such errors and defects free of charge and without any undue delay.

(9) With regard to fixed-price deliveries, both contracting parties shall be responsible for their own costs associated with the performance of acceptance testing. With regard to deliveries priced on the basis of working hours, the client shall, however, compensate the supplier for its work performed in relation to acceptance testing so that the supplier is responsible for its own costs associated with any re-testing performed due to the correcting of any possible errors.

(10) Unless otherwise agreed, the delivery shall be deemed to have taken place when the object of delivery has been accepted and the supplier has fulfilled all of its obligations under the agreement related to the rollout of the product or the end result of the service.

    5 Organisation and implementation of the delivery

(1) The contracting parties shall set up a project and a steering group for it for the fulfilment of the agreement and cooperation between the parties. Both contracting parties shall appoint their representatives to the steering group which supervises the implementation of the project as a cooperation organisation of the contracting parties. The tasks and authority of the steering group shall be specified in the agreement, and the group shall meet upon the request of a contracting party as necessary and at a minimum after each delivery phase. Minutes shall be maintained of the meetings of the steering group. The steering group may not amend the agreement.

(2) The supplier shall appoint a project manager whose task is to report on the state and progress of the project to the project's steering group. Other tasks shall be specified in the agreement. Both contracting parties shall appoint a contact person whose task is to monitor and supervise the fulfilment of the agreement and to communicate matters related to the fulfilment of the agreement within their organisation and to the other contracting party. Unless otherwise agreed, the supplier's project manager shall be the supplier's contact person. Each contracting party shall notify the other contracting party in good time if their contact person is replaced.

(3) The contracting parties shall appoint the required personnel resources to the project. Appointed key persons may be agreed upon in the agreement.

(4) The contracting parties shall each on their part reserve the necessary work premises and equipment for the project.

(5) A contracting party shall contribute to the implementation of the project in situations and contexts that are under the control of the said party. Both contracting parties shall make the decisions required to implement the project without delay.

(6) Unless otherwise agreed, the supplier shall produce the client's application and perform other tasks belonging to the project using the supplier's working methods.

(7) The contracting party responsible for the development environment shall be, during the project, responsible for taking the backup copies that are part of the object of the agreement and pertain to the object of delivery and for verifying that they are functional.

(8) The delivery project shall end once the object of delivery has been accepted and taken into use.

    6 The supplier's resources

(1) The supplier shall ensure on its part that a sufficient number of persons are available for the delivery.

(2) The supplier shall not replace the key persons named in the agreement without the client's permission for reasons other than those independent of the supplier. The client may not refuse from issuing its permission for such replacements without reasonable cause. The supplier shall always notify the client in advance in writing of replaced key persons and shall without delay name a new person in place of the person to be replaced.

(3) In terms of competence, the new person must fulfil the agreed requirements.

    7 Warranty

(1) During the warranty period, the supplier shall, free of charge and without any undue delay, correct any errors detected in the object of delivery. Corrections also include amending the documentation with changes corresponding to the corrections.

(2) The warranty period is six (6) months starting from the acceptance of the application by the client, unless otherwise agreed. If the client's application is accepted in stages, the warranty period for previously accepted stages will not expire until six (6) months have passed from the acceptance of the entire client's application.

(3) The client has the right to demand that, before the payment of the final instalment, the supplier lodges for the client a security accepted by the client regarding the fulfilment of the warranty obligations. The security shall be fifteen (15) per cent of the total price of the agreement inclusive of value added tax, and it must remain valid for at least three (3) months after the term of the warranty period under the agreement. In case of a delay in the fulfilment of the warranty obligations, the supplier shall extend the term of the warranty period. The supplier shall be responsible for all security-related costs.

(4) With regard to standard software, the warranty terms of the standard software in question shall be applied to the warranty.

(5) If an error detected in the object of delivery during the warranty period is caused by standard software, the supplier shall correct the error or have the error corrected at its own expense and according to its possibilities. If this is not reasonably possible, the supplier shall work around the error at its own expense. If creating a workaround is not reasonably possible through generally available means, the parties may agree upon additional work to work around the error, or the client shall be entitled to a price reduction. If the error is so significant that, due to the error, the purpose of the agreement remains essentially unfulfilled, the client shall have the right to cancel the agreement, unless the error concerns the standard software required by the client.

(6) The warranty shall expire to the extent the client modifies the client's application or the specified application environment without agreeing on it in writing with the supplier, or the client's application is used for purposes other than its intended purpose of use or in violation of instructions concerning its use, or the error is caused by some other reason attributable to the client.

    8 Rights

(1) The right of ownership to data media containing the applications that are the object of the agreement shall be transferred to the client once the data media have been delivered.

(2) The right of ownership and intellectual property rights to the client's material belong to the client or a third party, and they are not assigned to the supplier. The supplier shall have the right to process the client's material only for purposes pertaining to the fulfilment of the agreement.

(3) Unless otherwise agreed, copyright and intellectual property rights to the client's application and the associated documentation, the client's material excluded, shall belong to the supplier or a third party.

(4) The supplier shall grant the right to use the material delivered to the client without additional charges under the terms and conditions of open source code software. If the client and the supplier have not agreed upon the open source licence to be used, the supplier shall specify the open source licence to be applied. If several open source licences are applied to the material delivered, all licences must be mutually compatible.

(5) The supplier shall notify the client of the open source licence to be applied no later than before the delivery of the application or, if the client requests the supplier to specify the licence earlier, within thirty (30) days of the client's written request. If the supplier does not specify any licence, the supplier shall grant the client, without any additional charge, a royalty-free, permanent, irrevocable and non-exclusive right to, independently or with the assistance of an external service provider and without being limited by copyrights and intellectual property rights of the supplier or any third party:

      1. use the client's application for any purpose,
      2. modify and further develop the client's application,
      3. make copies of the client's application,
      4. distribute the copies, either in modified or unmodified form, to third parties, and
      5. transfer this right, or any part thereof, to third parties.

(6) The supplier assures that the client may utilise the aforementioned rights without being limited by any business or professional secrets of the supplier or a third party.

(7) The supplier and the client are entitled, without hearing the other party, to utilise the client's application and any material and know-how they have generated in conjunction with the agreement. This agreement does not remove the client's obligation to take any export limitations into account.

(8) The supplier must hand over the material to be delivered to the client.

(9) The supplier shall ensure that each and every licence in the material to be delivered is compatible with other licences in the material to be delivered and with the licence requirement specified by the client in the agreement, if any. The client commits to complying with the open source licence terms applicable to the material it has received.

(10) The supplier's liability for errors towards the client is determined based on the agreed purpose and extent of use, and nothing agreed regarding the client's rights in this Section 8 of these Special Terms and Conditions shall increase the supplier's liability for errors.

(11) Regardless of the open source code licence selected by the supplier, the supplier shall be responsible towards the client for any part of delivery it has made itself or contracted to its subcontractor as set out in Sections 6 (2) – 6 (7) of JIT 2015 – General Terms and Conditions.

(12) The delivery may include platform software if such software and the terms and conditions governing it have been specified in the agreement or if the client has later approved them. The provisions of Section 8 (4) do not apply to platform software which is governed by the applicable terms and conditions of standard software. The supplier shall not be liable towards the client for breaches of intellectual property rights associated with third-party platform software, except to the extent the third party in question has committed to the same towards the supplier under the standard terms and conditions of the platform software.

    9 The supplier's obligations

(1) The supplier shall be responsible for ensuring that the client's application and the documentation concerning it are in compliance with the agreement and that the work is carried out with the professional expertise required by the task and following good technical practices and a high quality level.

(2) The supplier shall cooperate and negotiate with any other suppliers and consultants used by the client, if the client so requests. Unless otherwise agreed, the supplier shall be entitled to charge for such additional work. However, the supplier must give an advance notification of any additional work thus resulting.

(3) The supplier shall define and design the object of delivery so that the client is able to convert, utilising automated systems as specified by the supplier, all of the client's material stored by the application into a format complying with the data material openness requirement.

(4) The supplier shall define and design the object of delivery so that the processing of personal data with the application complies with the requirements set by data protection legislation.

(5) The documentation of the object of delivery includes a data description. The supplier shall not be entitled to charge separately for the delivery of the data description, unless otherwise agreed.

(6) The supplier shall provide an open interface to the object of delivery if a requirement for an open interface has been agreed upon in the agreement.

    10 The client's obligations

(1) In addition to the client's tasks agreed in the agreement, the client shall provide the supplier with the information which the supplier requires in order to carry out its task and which can be turned over to the supplier. The client shall be responsible for the information, instructions and regulations it has issued to the supplier.

(2) The client shall be responsible for carrying out the tasks agreed upon in the agreement within the agreed schedule.

    11 Maintenance

(1) The supplier shall provide support and maintenance services for the object of delivery as agreed separately. The supplier commits to offering these support and maintenance services for the duration of at least one (1) year, starting from the acceptance of the client's application.

    12 Storing the source code of standard software

(1) If the client so demands, the supplier shall contribute to ensuring that the source code of the standard software included in the object of delivery, together with any modifications and additions made thereto for the client, is stored in the possession of an impartial provider of a source code storing service (an escrow agent) so that the client obtains the source code and the rights to use it in case:

      1. the holder of the rights to the standard software is declared bankrupt or placed into liquidation, or
      2. maintenance is not available for the object of delivery from the supplier, the right holder of the standard software in question, or from any third party, under terms and conditions substantially similar to those agreed upon by the supplier and client.

    13 Delays

(1) If a contracting party finds that it will be delayed in its delivery or in its performance of an obligation or considers such delay probable, the contracting party must, without delay and in writing, notify the other contracting party of the delay and its impact on the fulfilment of the agreement. The contracting parties shall agree upon a new delivery time, if required.

(2) If the delivery is delayed due to a reason under the responsibility of the supplier, the supplier shall pay a contractual penalty to the client for every commencing period of seven (7) days by which the supplier exceeds the due date agreed for the delivery or its part under the agreement. The penalty for each above-mentioned period shall be 0.5 per cent of the purchase price of the delayed object of delivery. However, the maximum penalty is 7.5 per cent of the afore-mentioned price. The amount of damage caused by the delay does not affect the amount of the penalty. A delay in the delivery of documents and information preventing the use of the object of delivery shall be considered comparable to a delay in the delivery of the product or service.

(3) The supplier shall not be entitled to receive a contractual penalty due to the client's delay.

    14 Open publication of the application

(1) The supplier shall publish the application within thirty (30) days of the acceptance of the object of delivery in a manner deemed appropriate by the supplier, unless otherwise separately agreed. The publication shall take place in a manner which supports version control so that the application to be published is publically available under the open source licence determined in accordance with Section 8 (4).

(2) If no licence has been determined in accordance with Section 8 (4), the supplier shall use the following licensing statement when publishing the application: "This program and its documentation are licensed under the EUPL 1.1 licence or, at the licensee’s option, any later version thereof." If the licensing of the parts used in the application to be published is not compatible with the EUPL 1.1 licence, the supplier shall use the following licensing statement with respect to these parts: "This program and its documentation are licensed under the MIT licence."

(3) The supplier shall copy and add the text of the applicable licences in connection with the application to be published.

(4) Insofar as the application to be published includes modifications of or expansions to parts of other open source code projects, such modifications and expansions shall primarily be published so that they are offered as contributions to the open source code project in question. In this respect, the supplier shall license the modifications and expansions in accordance with the practices of the open source code project in question. If publication is not reasonably possible in this manner, it shall, in any case, be carried out in accordance with Section 14 (1).

(5) Upon publishing the application, the supplier may announce extensive limitations of liability for the benefit of the supplier, but they shall not affect the supplier's liability towards the client under this agreement. Furthermore, this agreement shall not prevent the supplier, if it so desires, from being committed to a maintenance responsibility for the application to be published towards a third party.

(6) Prior to the publication and also during the maintenance of the application to be published, the supplier shall ensure that the application to be published does not include any of the client's confidential information or any other client-specific information, such as specifications, addresses, credentials or passwords related to the use of the information system. If required, the client shall contribute to specifying the information that is to be kept confidential.

(7) The supplier is obligated to publish information about the publication of the application to be published in the portal for compatibility descriptions and specifications maintained by the Finnish Government within thirty (30) days of the publication. The information shall, at minimum, include the publication date, a description and a location.

    15 Development model

(1) If so agreed in the agreement, the client may demand the supplier to develop the application to be published in a public version control system.

    16 Maintenance of the application to be published

(1) The supplier shall maintain the application to be published for a period of at least twelve (12) months starting from the acceptance of the object of delivery. Unless otherwise agreed, the maintenance shall include ensuring the availability of the application in accordance with Sections 14 (1) and 14 (2), and the entry of corrections to errors and of other modifications under the agreement into a public version control system at minimum at intervals of six (6) months as well as updates of information published in the portal in accordance with Section 14 (7) when necessary.

(2) The client and the supplier may agree upon extending the maintenance of the application to be published beyond the afore-mentioned scope. In such case, if the content of the extended maintenance of the application to be published is not agreed upon in more detail, the following terms and conditions shall be applied to the extended maintenance:

      1. In addition to the tasks set out in Section (1) above, the maintenance activities shall include general provision of information to third parties about the state and the development roadmap of the application. The supplier's obligation and the client's commitment shall be limited to the amount of work agreed upon.
      2. The supplier shall report to the client at agreed intervals and in the agreed manner or, unless otherwise agreed, at intervals of six (6) months, on any communications and actions taken and, at the same time, shall hear the client's opinions on further actions. The suppliers shall take the client's opinions, together with the opinions of any other user organisations, into account as it deems best. However, the supplier shall not have, unless otherwise agreed, the obligation to take concrete action on the basis of the client's opinions.
      3. The supplier shall have the right to invoice the extended maintenance of the application to be published from the client based on time spent and at agreed prices. If extended maintenance for the same application to be published is acquired by several parties, any single maintenance tasks shall be charged only once.
      4. Either contracting party may terminate the extended maintenance of the application upon three (3) months’ notice.