Software upgrades/modifications Sample Clauses
The 'Software upgrades/modifications' clause defines the rules and responsibilities regarding changes, improvements, or updates to software after its initial delivery. Typically, this clause outlines whether the provider is obligated to supply upgrades or modifications, the process for requesting or implementing such changes, and any associated costs or limitations. For example, it may specify if security patches are included or if major feature enhancements require separate agreements. Its core function is to set clear expectations between parties about ongoing software maintenance and evolution, thereby preventing disputes over future support and ensuring the software remains functional and secure.
Software upgrades/modifications. D.14.1 Software version enhancements must be initially introduced and tested between the Parties at test exchanges to ensure that there are no interworking problems before introduction into an active exchange. The Party making the software enhancement must give the other Party a minimum of two weeks written notice before testing can commence.
D.14.2 Unless otherwise agreed in writing between the Parties, a 30 Calendar Day lapse between a software upgrade in any switching unit and the general release into the rest of the network is required.
D.14.3 A controllable number of software patches should be activated in any 24 hour period on the same switching unit. The testing of such patches will be by mutual agreement in writing. All applications and tests must be completed in low traffic periods i.e., between 22:00 and 05:00 or at other times by mutual agreement in writing.
Software upgrades/modifications. D.15.1 Software version enhancements must be initially introduced and tested between the Parties at test exchanges to ensure that there are no interworking problems before introduction into an active exchange. The Party making the software enhancement must give the other Party a minimum of two weeks written notice before testing can commence.
D.15.2 Unless otherwise agreed in writing between the Parties, a 30 Calendar Day lapse between a software upgrade in any switching unit and the general release into the rest of the network is required.
Software upgrades/modifications. 23.2.1 To minimise the risk of interworking problems, upgrades to new software releases shall, prior to the introduction thereof into an active exchange, be tested at a test exchange. The Party wishing to introduce an upgrade shall give the other Party a minimum of 2 (two) weeks' written notice prior to the commencement of testing, at which point the Parties may agree whether it will be necessary for the other Party to participate in such testing.
23.2.2 Unless otherwise agreed in writing between the Parties, a 7 (seven) day lapse is required between a software upgrade in any switch and the general release into the rest of the network.
23.2.3 Patches shall, prior to the introduction thereof into an active exchange, be tested at a test exchange. A controllable number of software patches should be activated in any 24 (twenty four) hour period on the same switching unit. All tests and introductions of patches shall be done between 00h00 and 06h00 or during such other low traffic periods as may be agreed by the Parties.
Software upgrades/modifications. 4.9.1 To ensure that there are no interworking problems, software enhancements shall, prior to the introduction thereof into an active exchange, be introduced and tested between the Parties at a test exchange. A minimum of two weeks written notice shall be given before testing can commence.
4.9.2 Unless otherwise agreed in writing between the Parties, a 30 (thirty) day lapse is required between a software upgrade in any MSC or switching unit and the general release into the rest of the ECN.
4.9.3 A controllable number of software patches should be activated in any 24-hour period on the same switching unit. The testing of such patches will be by agreement in writing. All applications and tests shall be done between 22h00 and 05h00 or during such other low traffic periods as may be agreed.