{"id":671,"date":"2025-02-13T13:06:06","date_gmt":"2025-02-13T13:06:06","guid":{"rendered":"https:\/\/sapaddons.ingold-dev.com\/?page_id=671"},"modified":"2025-02-14T07:44:35","modified_gmt":"2025-02-14T07:44:35","slug":"ves-software-development","status":"publish","type":"page","link":"https:\/\/sapaddons.ingold-dev.com\/en\/ves-software-development\/","title":{"rendered":"VES – Software development"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Bitkom’s contractual terms for software development<\/h1>

1.\u00a0 Subject matter of the contract<\/h2>

1.1\u00a0 The provider shall develop software for the customer in accordance with the service description (see Item 2.2) underlying the concluded contract.<\/p>

1.2\u00a0 The copy of the software to be submitted to the customer by the provider contains only an executable form.<\/p>

1.3 The software shall be provided together with an operating manual (user documentation and\/or online help). The operating manual shall be drafted in the language of the software\u2019s user interface, unless agreed otherwise.<\/p>

Supply or creation of further documentation requires a separate written agreement, in particular, on the content and scope of the documentation.<\/p>

1.4\u00a0 The provider shall create the software and the operating manual (jointly: deliverables) in compliance with the principles of professional conduct.<\/p>

1.5\u00a0 Analysis, planning, consulting and training services are not the subject matter of this contract and are not owed by the provider.<\/p>

2.\u00a0 Collaboration between the contractual partners<\/h2>

2.1\u00a0 The customer shall notify the provider of the technical and functional requirements for the software in full and in detail, and supply the provider in a timely manner with all documents, information and data required for software development. This also includes a description of practical and suitable test cases and data for validation of attributes (item 7.1).<\/p>

2.2\u00a0 The\u00a0service\u00a0description\u00a0shall\u00a0finally\u00a0convey\u00a0the required software attributes. The service description shall only be amended in accordance with Item 3. The provider shall render analysis, planning and consulting services, also in connection with the service description, only on the basis of a separate contract in exchange for separate remuneration (also see item 1.5).<\/p>

2.3\u00a0 The provider shall engage the customer’s designated contact person (item 2.1 of the document titled ‘AV Bitkom’ – as a project manager, insofar as required for contract execution. The decisions made by the contact persons must be documented in writing.<\/p>

2.4\u00a0 The customer has no claim to service provision at their own premises.<\/p>

3.\u00a0 Procedure for changes to services<\/h2>

Both contractual partners can recommend changes to the service description (item 2.2) and service provision. The following procedure is agreed for this:<\/p>

3.1\u00a0 The provider shall preview the customer’s recommendation for change and inform them whether or not a detailed assessment of this recommendation is necessary.<\/p>

3.2\u00a0 If a detailed assessment of the recommendation for change is necessary, the provider shall inform the customer in a timely manner about the expected, necessary period of time and the remuneration. The customer shall accept or reject the assessment mandate within a reasonable period of time.<\/p>

3.3\u00a0 If a detailed assessment of the recommendation for change is not necessary or the mandated assessment has been completed, the provider shall either<\/p>

  • submit a written offer concerning implementation of the changes (change offer) to the customer. The change offer encompasses, in particular, amendments to the service description and their effects on the service period, planned deadlines and remuneration; or<\/li>
  • inform the customer that the recommendation for change cannot be implemented within the scope of the agreed services for the provider.<\/li><\/ul>

    3.4\u00a0 The\u00a0customer\u00a0shall\u00a0either\u00a0reject\u00a0a\u00a0change\u00a0offer within an acceptance period specified therein (binding period) or declare acceptance in writing or another form agreed between the contractual partners. The customer shall promptly notify the provider of any rejection.<\/p>

    3.5\u00a0 The provider and customer can agree that services affected by a recommendation for change be interrupted until the end of the assessment, or – if a change offer is submitted – until expiry of the binding period.<\/p>

    3.6\u00a0 Until an offer for change is accepted, work shall continue on the basis of the previous contractual agreements. The service periods are extended by the number of calendar days in which work was interrupted in connection with the recommendation for change or its assessment. The provider can request a reasonable remuneration for the duration of the interruption (item 3.5), unless the provider uses their employees affected by the interruption in a different way or wilfully refrains from use.<\/p>

    3.7\u00a0 On request by the provider, the change procedure is to be documented in writing or in text on one of the provider\u2019s forms, unless agreed otherwise. Any modification to the service description shall be agreed in writing or another form by the contractual partners.<\/p><\/div>

    3.8\u00a0 Items 3.2 through 3.7 apply accordingly to the provider\u2019s recommendations for change.<\/p>

    3.9\u00a0 Recommendations for change must be addressed to the contractual partner’s contact person (item 2.3).<\/p>

    4.\u00a0 Rights of use and protection against unauthorized use<\/h2>

    4.1\u00a0 On full payment of the owed remuneration, the provider shall grant the customer a non-exclusive right to use the deliverables within their enterprise in perpetuity, within the contractually intended scope of use, unless agreed otherwise. Transfer of rights of use to third parties is only permitted if the customer completely relinquishes these rights. The customer undertakes to impose the obligations and restrictions of use relevant to them on the third party. This applies especially to the obligations as set forth in item 5.8. On the provider’s request, the customer shall confirm relinquishment of own use in writing.<\/p>

    4.2\u00a0 Otherwise all rights remain with the provider.<\/p>

    4.3\u00a0 The provider is authorized to take appropriate technical measures to prevent use contrary to the contract. Use of the software in an alternative or subsequent configuration must not be significantly affected by this.<\/p>

    4.4\u00a0 The provider can revoke the customer\u2019s right of use if they significantly breach the restrictions of use or other rules on preventing unauthorized use (see also item 5.8). The provider shall set a grace period of remedy for the customer beforehand. In the event of recurrence and in special circumstances which justify immediate revocation, bearing in mind the interests of both sides, the provider can also declare revocation without setting a deadline. After revocation, the customer shall give the provider written confirmation that use has been suspended. The provider shall restore rights of use for the customer after they have submitted and assured in writing that there are no more breaches of these rights of use, and previous breaches as well as their consequences have been eliminated.<\/p>

    5.\u00a0 Customer’s obligations<\/h2>

    5.1\u00a0 The customer shall ensure that specialist staff are available for supporting the provider during the project, for validation of attributes (item 7.1) following handover, and for deployment of the software.<\/p>

    5.2\u00a0 At the provider\u2019s request, the customer shall supply suitable test cases and data for validation of attributes in a machine-readable form (see item 2.1). If the customer fails to supply such test cases and data, the provider may select and develop suitable test cases independently in exchange for additional remuneration.<\/p>

    5.3\u00a0 The customer undertakes to download software provided for this after notification of availability.<\/p><\/div>

    5.4\u00a0 The customer shall report defects, especially as set forth in item 2.4 of ‘AV Bitkom’. The provider’s relevant forms and procedures shall be used for this purpose, unless agreed otherwise.<\/p>

    5.5\u00a0 The customer shall support the provider to the extent necessary during contract execution and rectification of defects as per item 2.2 of ‘AV Bitkom’, and supply other analysis material.<\/p>

    5.6\u00a0 The customer shall promptly inform the provider about any changes in operating conditions following handover.<\/p>

    5.7\u00a0 Unless agreed otherwise, the customer shall additionally store, at their premises, all documents, information and data submitted to the provider in such a way that these can be reconstructed using data media in the event of damage or loss.<\/p>

    5.8\u00a0 The customer must not undertake anything which might facilitate unauthorized use. In particular, the customer must not attempt to decompile software unless they are authorized to do so. The customer shall promptly inform the provider if said customer becomes aware that unauthorized access is imminent or has occurred in their sphere.<\/p>

    6.\u00a0 Handover and transfer of risk<\/h2>

    6.1\u00a0 Unless agreed otherwise, the provider may also supply the customer with deliverables via electronic transmission or as downloads. If deliverables are made available as downloads, the provider shall notify the customer of this.<\/p>

    6.2\u00a0 Insofar\u00a0as\u00a0deliverables\u00a0are submitted electronically, the risk of accidental loss is transferred to the customer on receipt by the telecommunications operator which the provider has tasked with forwarding.<\/p>

    6.3\u00a0 Insofar as deliverables are made available for downloading, the risk of accidental loss is transferred to the customer on availability and related notification for said customer.<\/p>

    7.\u00a0 Validation of attributes and customer’s claims due to defects<\/h2>

    7.1\u00a0 The customer shall examine all supplied deliverables, in particular, software or executable software components agreed as partial deliveries, immediately – as a rule within 14 calendar days – for absence of defects and, in particular, presence of the contractually agreed attributes (validation of attributes). To this end, the customer shall use test cases and data practical and suitable for the software (see item 2.1). The provider can perform coordination with the customer as regards test procedures, besides attending and supporting the validation of attributes on-site.<\/p><\/div>

    7.2\u00a0 Defects occurring during or after validation of attributes will be reported duly by the customer without delay, but no later than seven calendar days from discovery (item 5.4).<\/p>

    7.3 Applicable additionally is the commercial examination and defect notification obligation (section 377 German Commercial Code).<\/p>

    7.4\u00a0 The provider shall guarantee that the deliverables possess the contractually agreed attributes during contractually compliant use. Item 4 of the document titled ‘AV Bitkom’ applies additionally to material defects. Item 5 of the document titled ‘AV Bitkom’ applies additionally to defects of title. Section 650 (2) German Civil Code remains unaffected.<\/p>

    7.5\u00a0 The customer may assert claims due to defects only if the reported defects can be reproduced or proven in another way. Items 5.4, 7.2 and 7.3 apply, in particular, to reporting of defects.<\/p>

    7.6\u00a0 If the customer is entitled to claims due to defects, said customer initially only has a right to supplementary performance within a reasonable period. Supplementary performance includes, at the provider’s discretion, either remedy or production of a new deliverable. The customer’s interests are to be considered adequately in the choice.<\/p>

    The customer shall enable installation and removal for the provider in the scope of supplementary performance, unless this is unreasonable for the customer. Before taking own measures to remedy defects, the customer shall consult the provider.<\/p>

    Any entitlement of the customer’s to reimbursement of expenditure is limited to a reasonable extent, taking into consideration the value of the relevant performance in faultless condition and the significance of the defect.<\/p>

    7.7\u00a0 If supplementary performance fails or cannot be implemented for other reasons, the customer can reduce remuneration in accordance with legal requirements, rescind the contract and\/or request compensation for damages or expenditures – within the scope of item 6 of ‘AV Bitkom’.<\/p>

    If supplementary performance is delayed, item 3.4 of ‘AV Bitkom’ applies to the provider\u2019s compensation for damages and expenditures. Item 6 of ‘AV Bitkom’ applies, in particular, to compensation for damages and expenditures.<\/p>

    The customer shall exercise a right of choice to which they are entitled regarding these claims due to defects within a reasonable period, generally within 14 calendar days from the time of being able to realize the customer’s right of choice.<\/p>

    8.\u00a0 Validity of ‘AV Bitkom’<\/h2>

    Bitkom’s general contractual terms (document titled ‘AV Bitkom’) apply additionally.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

    Bitkom’s contractual terms for software development 1.\u00a0 Subject matter of the contract 1.1\u00a0 The provider shall develop software for the customer in accordance with the service description (see Item 2.2) underlying the concluded contract. 1.2\u00a0 The copy of the software to be submitted to the customer by the provider contains only an executable form. 1.3 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"template-cms.php","meta":{"inline_featured_image":false,"footnotes":""},"class_list":["post-671","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/sapaddons.ingold-dev.com\/en\/wp-json\/wp\/v2\/pages\/671","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sapaddons.ingold-dev.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sapaddons.ingold-dev.com\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sapaddons.ingold-dev.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sapaddons.ingold-dev.com\/en\/wp-json\/wp\/v2\/comments?post=671"}],"version-history":[{"count":8,"href":"https:\/\/sapaddons.ingold-dev.com\/en\/wp-json\/wp\/v2\/pages\/671\/revisions"}],"predecessor-version":[{"id":809,"href":"https:\/\/sapaddons.ingold-dev.com\/en\/wp-json\/wp\/v2\/pages\/671\/revisions\/809"}],"wp:attachment":[{"href":"https:\/\/sapaddons.ingold-dev.com\/en\/wp-json\/wp\/v2\/media?parent=671"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}