Product Lifecycle

End of Product Life Cycle: Overview

Products reach the end of their Product Life Cycle for a number of reasons. These reasons may be due to market demands, technology innovation, and development driving changes in the product, or the products simply mature over time and are replaced by functionally richer technology.

While this is an established part of the overall product life cycle, NETRONIC Software recognizes that end-of-life milestones often prompt companies to review the way in which such end-of-sale and end-of-life milestones impact the usage of their NETRONIC Software products in their companies. With that in mind, we have set out below NETRONIC Software's end-of-life policy to help customers better manage their end-of-life transition and to understand the role that NETRONIC can play in helping to migrate to alternative NETRONIC offerings.

Product Life Cycle Milestones

The following milestone definitions apply to all EOL policies:

End-of-Life (EOL)

Announcement milestone – the date on which NETRONIC Software announces via website and blog posting, that a specific product has reached his EOL. The EOL announcement provides dates by which time Marketing, Sales, development, and overall maintenance/support will end for the affected product.

End of Sales and Marketing (EOSM)

The date until which – after the EOL – customers and prospects still can purchase new and upgrade licenses for the respective product; as well as they can agree new maintenance period until the end of the service period (EOS). As a general rule, the EOSM period following the EOL announcement will be a minimum of 3 months, if NETRONIC still observes a reasonable market demand for that product. During this period, the product will no longer get functionally enhanced. However, NETRONIC Software will provide bug fixes for reported bugs of the most current version at the EOL announcement. NETRONIC Software also will eventually publish Service Releases of the most current product version.

End of Service (EOS)

The final date for support via maintenance contracts. As a general rule, the period between EOL and EOS will be a minimum of 2 years, but could also be much longer (or shorter in exceptional cases). In the period between EOSM and EOS, no new software licenses of the affected products are available. NETRONIC Software will provide bug fixes for reported bugs of the most current version at the EOL announcement. NETRONIC Software also will eventually publish Service Releases of the most current product version.

Current EOL-Products

Add-ins for Microsoft Dynamics NAV (C/AL integration)

In December 2021, we decided to align our product lifecycle management with Microsoft's (modern) lifecycle.

Read this blog post to learn all the details of this decision.

As a consequence of this decision, the following milestone dates apply.

Visual Production Scheduler (VPS) for Dynamics NAV

Visual Jobs Scheduler (VJS) for Dynamics NAV

Visual Service Scheduler (VSS) for Dynamics NAV

Extensions for Microsoft Dynamics 365 Business Central (AL integration)

In December 2021, we decided to align our product lifecycle management with Microsoft's (modern) lifecycle.

Read this blog post to learn all the details of this decision.

As a consequence of this decision, the following milestone dates apply.

Visual Advanced Production Scheduler (VAPS), and Visual Production Scheduler (VPS) and Visual Jobs Scheduler (VJS) for Dynamics 365 Business Central

VARCHART and GRANEDA product family

VARCHART XGantt, XNet, and XTree

Maintenance services for VARCHART XGantt, XNet and XTree are provided under the following conditions:

1. We ensure that VARCHART XGantt, XNet, and XTree continue to run only on Microsoft Windows versions running on x86 or x64 processors that support .NET Framework 2.x, 3.x or 4.x, and for which Microsoft has not reached the end of support. Other .NET Framework versions not mentioned here are explicitly not supported, and will not.

2. We ensure that VARCHART XGantt, XNet, and XTree continue to run only with Microsoft Visual Studio versions running on x86 or x64 processors that support .NET Framework 2.x, 3.x or 4.x, and whose support has not been discontinued by the provider. The same applies to any other development environment.

VARCHART JGantt

Resource Scheduling Module

VARCHART XGantt/ XNet/ XTree ASP.NET Edition

GRANEDA Dynamic 4.2