Release policy

Generation release (every 3-4 years)

A Generation version release is specified by the first digit of the version number (ex. version 5.0 -> version 6.0 etc). A new generation is based upon major changes to the platform like a new GUI model or major changes to the database structure or the overall architecture. The timeframe for a Generation update is approximately 3-4 years.

Major version (yearly)

A Major version release is specified by the second digit of the version number (ex. version 5.1 -> 5.2) and is normally released annually including major new modules like Asset Management, Claims and other features that impacts new major functionality to the platform. Most of them are not included in the standard platform price and must be bought as an addon to the platform.

Minor version (4-8 times pers year)

A Minor version release is specified by the third digit of the version number (ex. version 5.1.1 -> 5.1.2) and is released 4 to 8 times per year. These updates include minor Feature updates, Bug fixes and Security updates.

Software Patches (as needed)

A Software patch is a temporary resolution for Priority 1 Software Failures. These releases are made available on an ‘as needed’ basis only and will not automatically be made available to a site until they are rolled up into a Minor Release. A software Patch does not impact the version number as it is only a temporary solution for a Priority 1 situation.

Release notification

During the term of an active Maintenance Agreement Customers will be notified by e-mail whenever a new Major, Minor update/release for the Software is available for download. Release notes can be found at the Signifikant Knowledgebase.

Licensing

The delivery to Company of a Release will not increase the total number of licenses of the Software to which Company is entitled. After installation of the Release, this Agreement will only apply to that Release. Company agrees to destroy or archive (and NOT use or transfer) prior versions of the Software.