Price Plan "CFT Platform and Applications"
Effective since May 1, 2014
(for CFT-Bank, CFT-Retail Bank, CFT-Management Accounting, CFT-Budget Performance Monitoring, CFT-Electronic Archive, CFT-Insurance Company, CFT-Corporation).
1 The LICENSEE may create and modify Local Objects on its Production Scheme (or several Production Schemes, if the license agreement provides for the LICENSEE’s right for the use of several Production Schemes) in respect of the limitations fixed by the terms and conditions of the license agreement between the LICENSEE and the LICENSOR. If the LICENSEE is interested in using additional SYSTEM copies (i.e. in excess of the number of Production Schemes fixed by the terms and conditions of the effective license agreement) for creation of new and modification of existing Local Objects, the LICENSEE must conclude a separate agreement (with receipt of the status “Application Developer”) providing for the LICENSEE’s right for the use of additional SYSTEM copies for creation and modification of Local Objects in accordance with the Price Plan “CFT API”. Alongside with this, if the percent ratio of the Local Objects fixed in the Control License Report (CLR) in the LICENSEE’s Production Scheme 5 to the total amount of Application Objects within the Applications, the rights for the use of which are acquired by the LICENSEE:
(i) does not exceed 2%,
(ii) does not exceed 10%, but the LICENSEE either
(a) pays a monthly license payment for the SYSTEM in the amount of 2.5 % or more of the one-time license payment provided for by this Price Plan, or
(б) pays a monthly license payment in the amount of 2.5 % per month of the one-time license payment for all new Applications licensed by the LICENSEE from the current Application Catalog, and monthly increases the current value of the Periodical License for all earlier licensed Components (including the Platform and Applications), in respect of the number of users (and other license parameters, if applicable) not less than by 2 % as compared to the previous month, until the value reaches 2.5 % per month of the cost (value of one-time license payment) of all Components earlier licensed by the LICENSEE (including the Platform and Applications) in respect of the number of users (and other license parameters, if applicable), provided for by the Price Plan. Thus if the terms and conditions of the effective license agreement already provide for indexation of the periodical license payment, the growth value of the periodical license payment per each calendar month is deemed the maximum of the two values – value determined by the terms and conditions of the license agreement, and value stated above (2%),
2 One-time license payment is paid according to the concluded license agreement, which states the initial number of Applications, users and other SYSTEM licensing parameters. If the value of the parameter increases, on which the size of one-time license payments depends, the LICENSEE pays the difference between the cost of earlier acquired right for the use of a respective licensing object (size of one-time license payment) and new cost calculated according to the Price Plan as of the last day of the reporting period (month) in which the parameter was raised. In this case the values of respective parameters are recorded in the Control License Report. The amount of license payments is assessed based on the maximum parameter values recorded in the Control License Report (CLR) during one month.
If the LICENSEE licensed Platform 1 earlier:
NoU is the number of users recorded in the CLR for the reporting period before the start of the use of Platform 2MCA,OLPactual is the average size of one-time license payment paid by the LICENSEE for the use of Platform 1 by one User. The average size is calculated as the total amount of all one-time license payments for Platform 1 / Users during three years before the transfer to Platform 2МСА or from the effective period of the license agreement (if as of the transfer to Platform 2MCA it was effective for less than 3 years),in other cases the standard conditions of this Price Plan apply.For Applications not included in the fixed set of Applications selected by the LICENSEE (included in the License Package specified in the license agreement as of the time of its signing), there is a Test Period. Test Period is the period from the start of the use of a respective Application till the last calendar day of the month in which this Application was first recorded in the Control License Report. During the Test Period the LICENSEE may use the Application on the terms and conditions of the effective license agreement. The LICENSEE may waive to use an Application at any moment before the end of its Test Period without payment of license payments for the use of the Application during the Test Period. If after the end of the calendar month following the month, in which the event of the start of Use of any Application was recorded in the CLR, the CLR confirms the fact of continuation of the use of this Application in the LICENSEE's Production Scheme, after the end of the calendar month following the month of the first record about the event of the start of Use of the respective Application in the CLR, the LICENSEE is obliged to pay the first license payment for the specified Application, pay the double one-time license payment specified in the Application Catalog for this Application, for the use of the Application during the Test Period and the following calendar month of the Application use, and from the third calendar month to pay the monthly license payment for the Use of the Application. The size of one-time license payment is determined according to the price specified in the Application Catalog for the respective Application as of the last calendar month of the reporting period (month) in which the LICENSEE started to use the Application in the Test Mode, and the size of monthly payments is determined according to the rules specified in column "Monthly License Payment" in the table above. If the LICENSOR does not receive the payment for the Applications within the period stipulated by the license agreement and this Price Plan, the LICENSOR is entitled to deprive the LICENSEE of the technical opportunity to use these Applications until they are paid for, or take other measures provided for in the license agreement and the current legislation. The LICENSEE may use the Test Period for each Application but not more than once for each Application within the license agreement effective period. For certain Applications the duration of the Test Period can be different, or there can be no Test Period. Information on the lack or different duration of the Test Period is given in the Application Catalog. The LICENSOR may at any moment unilaterally raise, lower or cancel the Test Period for any Applications. The information about the change/cancellation of the Test Period is posted in the Application Catalog. Thus the LICENSEE that uses a respective Application in the Test Period at the time of such change or cancellation is entitled to use it until the end of the Test Period which was established at the start of the use of this Application by the LICENSEE.
3 The monthly license payment is effected from the month following the month in which the license agreement was signed. The monthly license payment is not effected for Additional Applications.
If parameters are changed, on which the size of monthly license payments depends, their actual number is recorded in the LICENSEE's Production Scheme and in the LICENSEE's Control License Report. The amount of monthly license payments is assessed based on the maximum actual number of respective parameters recorded in the Control License Report during the reporting month. 4 A different size of the periodical (monthly) license payment can be determined for certain Applications in the Application Catalog. 5 Local Objects that comply with at least one of the following conditions are excluded from the calculations: (1) registered by the LICENSOR before the cancellation of such registration on November 01, 2013,(2) Local Objects registered by the LICENSOR and created by it in the LICENSEE’s Production Scheme.
From January 01, 2013, new Local Objects created by the LICENSEE are not registered. Thus the LICENSEE will be provided a technical certificate allowing to modify Local Objects created by the LICENSEE and registered by the LICENSOR before January 01, 2013.