Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »


VIII. Maintenance and Support 

Platform Support Guideline

Our platform differentiates between platform releases, extension packs, and service packs. Platform releases would happen every 18-24 months depending on content changes and market requirements. Within this frame, several Extension Packs and Service Packs are provided.

Platform Releases

Are a new release of the Licensed Software with significant changes. It is shown as a change in the digit(s) to the left of the decimal point in the Licensed Software number [(x).xx]. 

Generally, Platform Releases:

  • Backward compatibility: Should be assured with previous versions. However, Platform Releases might come along with significant API changes and API additions that would require refactoring of applications built against these APIs - Migration efforts in the field: Platform Releases trigger potentially migration efforts in the field from the previous to the current version 

Service Packs

Are a new release of the Licensed Software that incorporates bug fixes and minor changes. It is shown as a change in the second digit to the right of the decimal point in the applicable Licensed Software number [x.x (x)]

Generally, Service Packs:

  • Backward compatibility: Full backward compatibility with the previous version

  • Migration efforts in the field: Updates from the previous version should trigger no migration requirements in the field (exceptions may occur) 

Extension Packs

Are a new release of Licensed Software with enhancements and functional improvements. It is shown as a change in the first digit to the right of the decimal point in the applicable Licensed Software number [x. (x) x]

Generally, Extension Packs:

  • Backward compatibility: Full backward compatibility with the previous version

  • Migration efforts in the field: Updates from the previous version should trigger no migration requirements in the field (exceptions may occur)

    • New functionality might trigger new engineering efforts but only to enable that functionality 

J2 Innovations provides support for its current and partly for previous versions of FIN Framework:

  • Current platform version [x]: Extension Packs and Service Packs

  • Previous platform version [x-1]: Service Packs with focus on Cyber Security and major bug fixes and other optimizations

  • Older platform version [x-2FF]: No support 

Exceptionally, with FIN 5, we will not provide further support of FIN 4.5 through Service Packs. 

General Maintenance Guideline

Maintenance is a key ingredient in our strategy to keep customers always up-to-date with our latest innovation and assures that the product is following the latest requirements of Cyber-Security, system stability and system compatibility with the latest Operating Systems (e.g. Windows, LINUX, Java). 

Customers that have their en re-license (incl. all products) under Maintenance get access to:

  • Platform Releases: Yes

  • Extensions Packs: Yes

  • Service Packs: Yes 

Customers that do not have Maintenance get access to:

  • Platform Releases: No

  • Extensions Packs: No

  • Service Packs: No

Note: Platform Releases, Extension Packs, and Service Packs are provided via secure download. OEMs / distributors are informed by Sales about new releases and new builds being provided via E-Mail. 

Maintenance purchase for FIN Framework is different, depending on the deployment:

  • Deployed on a server or industrial PC: Generally, circa 18% of the then-current product license price, the exact price can be taken from the then-current price list - Deployed on OEM embedded hardware: Maintenance is generally included, provided that the customer has an active Distribution contract. Maintenance is only provided through the original supplier of the OEM embedded hardware product. 

  • The ini al 12 months after a product was licensed include Maintenance. After this date, Maintenance needs to be purchased. In order to get access to Maintenance for an instance, all products that the license consists of the need to be under Maintenance. 

Example: Customer purchases in Jan 2019 100 CAPs, March 2019 100 CAPs and April 2019 100 CAPs which are within one license and provided into one instance (and Host ID). In order to receive Maintenance for this instance, the Customer needs to have all three line-items under Maintenance on the day of updating or upgrading the installed software. 

Pro Rata Concept:

In order to simplify Maintenance, all licensed products are due on January 31st of the Calendar Year. After the 12 months courtesy period, Customer needs to pay the ini al X months un l January 31st pro rata versus a full year purchase. After this date, Maintenance renewal is due every year again on January 31st, paid forward for minimum a full 12 months. Through this, the process effort of renewal is reduced for our OEMs / distributors and their System Integrators / Installers. 

Example: Customer purchases in October 2019 100 CAPs. For the ini al 12 months un l October 2020, maintenance is included in the ini al purchase. For the period from October 2020 to January 31st, 2021, 3/12 of the Maintenance are due (pro rata for Nov/Dec/Jan versus full 12 months). After this, another 12 months Maintenance can be purchased un l Jan 31st, 2022, and after this another 12 months un l Jan 31st, 2023. 

Important: For those CAPs within a license and instance that have been bought prior to the release of FIN 5 (and the new price list), the Maintenance due forth-going is only on the purchased CAPs. In this case, we will free of charge stock-up to 100% HIS tags un l July 31, 2021. 


  • No labels