Definitions

  • “HSONN” is HSO Innovation.
  • “Software” or “HSONN Software” means the standard Intellectual Property as specified in Section 1 and supplied by HSONN and excludes Third Party Software.
  • “Current Program” means the Versions, Major and Minor Releases and Maintenance Releases of the Software supported by HSONN.
  • “Version” means a set of the Software designated by HSONN of the same generation in which substantial new functionalities or other substantial changes are introduced e.g. DYS-SMA 5.0.x for Microsoft Dynamics AX2009 to DYS-SMA 6.0.x for Microsoft Dynamics AX2012 or DYS-SMA 6.0.x for Microsoft Dynamics AX2012 to DYS-SMA 6.2.0.x for Microsoft Dynamics AX2012R2 or DYS-SMA 6.3.x for Microsoft Dynamics AX2012R3. A Version is containing substantial restructuring and major new functionality to the Software.
  • “Major Release” means a set of the Software designated by HSONN in which in addition to possible correcti­ons of detected shortcomings, functional enhancements have been included e.g. DYS-SMA 6.3.4xx for Microsoft Dynamics AX2012R3 to DYS-SMA 6.3.5xx for Microsoft Dynamics 365 for Finance and Operations. A Major Release might also contain a substantial restructuring and major new functionality to the Software.
  • “Minor Release” means a set of the Software designated by HSONN in which in addition to possible correcti­ons of detected shortcomings, small functional enhancements have been included e.g. DYS-SMA 6.3.5xx for Microsoft Dynamics AX2012R3 to DYS-SMA 6.3.5yy for Microsoft Dynamics 365 for Finance and Operations AX7.XX. A Minor Release is containing some new Software functionality and bug-fixes.
  • “Maintenance Release” means a set of the Software designated by HSONN in which detected shortcomings are being remedied e.g. DYS-SMA 6.3.500 Build 2104 for Microsoft Dynamics AX 2012 R3 to DYS-SMA 6.3.500 Build 2506 for Microsoft Dynamics AX2012R3 or DYS-SMA 6.26.500 Build 2104 for Microsoft Dynamics AX 2012 R2CU6 to DYS-SMA 6.27.400 Build 2506 for Microsoft Dynamics AX2012R2CU7. A Maintenance Release is containing bug-fixes to existing functionality.
  • “Expired Program” means Software that is not a Current Program.

Lifecycle Support

Software lifecycle policy and list of releases

Starting with the release of Microsoft Dynamics 365 for Operations version 1611, application versions are supported for three (3) years from the initial date of a Major release, as specified in Table 1. Major releases by HSONN will typically be based on major releases by Microsoft. Minor releases are subsequent releases, introducing non-critical functionality or other aspects. Support of Minor releases will expire when the preceding Major release expires. Major and Minor Releases will be introduced on a specific Platform Update, which is the earliest supported Platform Update for that release. Platform Updates maintain backward compatibility with the application versions that are supported at the time of the Platform release within the (3 year) application support lifecycle.

Table 1: List of releases

HSONN Product
Release
 Major/ Minor
Based on D365
Platform Update
Initial date
Expiration
Comments
Service Management
DYSSMA 7.312.730
Major
Dynamics 365 for Finance and Operations, 7.3
PU12
Feb 2018
Feb 2021
Service Management
DYSSMA 720.780.730
Major
Dynamics 365 for Finance and Operations, July 2017
PU8
Sept 2017
Sept 2020
Service Management
DYSSMA 710.740.730
Minor
Dynamics 365 for Operations, 1611
PU4
May 2017
Jan 2020
Service Management
DYSSMA 710.730.720
Major
Dynamics 365 for Operations, 1611
PU3
Jan 2017
Jan 2020
Maintenance Management
DYSEAM 7.312.730
Major
Dynamics 365 for Finance and Operations, 7.3
PU12
Jan 2018
Jan 2021
Maintenance Management
DYSEAM 720.780.730
Major
Dynamics 365 for Finance and Operations, July 2017
PU8
Sept 2017
Sept 2020
Maintenance Management
DYSEAM 710.730.720
Major
Dynamics 365 for Operations, 1611
PU3
Jan 2017
Jan 2020
Rental Management
DYSRMS 7.312.xxx
Major
Dynamics 365 for Finance and Operations, 7.3
PU12
Feb 2018
Feb 2021
Rental Management
DYSRMS 720.7100.1000
Minor
Dynamics 365 for Finance and Operations, July 2017
PU10
Dec 2017
Sept 2020
“Ella” release
Rental Management
DYSRMS 720.760.800
Major
Dynamics 365 for Finance and Operations, July 2017
PU8
Sept 2017
Sept 2020
Rental Management
DYSRMS 710.730.720
Major
Dynamics 365 for Operations, 1611
PU3
Jan 2017
Jan 2020
Graphical Planning & Scheduling
DYSGPP 7.312.730
Major
Dynamics 365 for Finance and Operations, 7.3
PU…
Feb 2018
Feb 2021
Graphical Planning & Scheduling
DYSGPP 720.7110.730
Minor
Dynamics 365 for Finance and Operations, July 2017
PU11
Nov 2017
Sept 2020
PU11 release to support CoC
Graphical Planning & Scheduling
DYSGPP 720.780.730
Major
Dynamics 365 for Finance and Operations, July 2017
PU8
Sept 2017
Sept 2020
Banking
DYSBNK xxx.xx.xxx
Major
Dynamics 365 for Finance and Operations, 7.3
PU…
Jan 2018
Jan 2021
Banking
DYSBNK xxx.xx.xxx
Major
Dynamics 365 for Finance and Operations, July 2017
PU8
Sept 2017
Sept 2020
Banking
DYSBNK xxx.xx.xxx
Major
Dynamics 365 for Operations, 1611
PU3
Jan 2017
Jan 2020
Advanced Field Service
DYSAFS 2.0
Major
Dynamics 365 Customer Engagement, Field Service
n.a.
Feb 2018
Feb 2021
Advanced Field Service
DYSAFS 1.0
Major
Dynamics 365 Customer Engagement, Field Service
n.a.
Aug 2017
Aug 2020

One Version

Provided that a customer is current with their payments, the customer is entitled to new releases of the product. HSONN will not provide individual hotfixes but will provide customers with new releases, containing all cumulative fixes and/or new features.

When Microsoft releases a new major version of Dynamics 365 (‘Spring’ and ‘Fall’ releases), HSONN is committed to provide a compatible release of her products within 2 weeks of the official release date by Microsoft. As a member of Microsoft’s PEAP program, HSONN is able to recognize disruptive changes early on, and act upon them.

HSONN will check compatibility with the monthly updates of Dynamics 365. If HSONN needs to create a new release to ensure compatibility, such a release will be available within 1 week of the official release date by Microsoft. Compatibility is checked using RSAT and other automated tests. Testing is done with Microsoft flighted features switched off.

If HSONN decides to deprecate products or major features of products, it will announce this 1 year in advance, using the company newsletter.