5 Things You Need to Know about Avaya’s Product Lifecycle

Happy April, readers!

As I look out my window, the signs of spring are finally here. The temperatures are (mostly) staying above freezing here in Massachusetts and nature is starting to stir. Despite the cold winter we had, I’ve always been a fan of having all four seasons: it provides a cycle, a slow-moving rhythm if you will.

This cycle of life is also present at Avaya, in that our products eventually become old and enter our lifecycle policy. These past few months, I’ve read through hundreds of lifecycle notifications and I know it can be confusing at times, so I wanted to explain how the Avaya Lifecycle works.

Product Lifecycle Chart

End of Sale
After a product has been on the market for a period of time, Avaya’s Product Management team determines the need to end the sale of that product. Depending on the product, we strive to give between two and nine months advance notification via an End-of-Sale Notification.

A good example of one is the announcement from January for the Avaya A175 Video Desktop Device. The notice includes the pertinent dates as well as the migration strategy.

Manufacturer Support
After a product has reached its End of Sale date, it enters manufacturer support. During this period of time, products continue to be supported by Avaya, including patches and updates as necessary. Both the Support and Development organizations are engaged in troubleshooting and resolving customer issues. All that has changed is that we are no longer making the products available for sale.

Extended Services Support
When a product ends the Manufacturer Support period, a Services Support Notice (SSN) will be issued that announces the beginning of Extended Services Support (ESS).

During this period, customers with maintenance contracts continue to get support from Avaya, but no further changes to the product (patches, updates, etc.) will be made.

In effect, the Development organization moves on to other releases, but the Support organization continues to provide support. An example SSN for Avaya Aura System Manager 1.0 can be downloaded here.

This period typically lasts 3 years for hardware and 5 years for software, but can be shorter or longer depending on a variety of factors including availability of replacement parts.

End of Services Support
The final chapter in a product’s lifecycle is reached when the ESS period ends with a final SSN being released announcing the End of Services Support. The SSN will include a date at which point Avaya will no longer provide maintenance support for any customers.

An example can be found here.

As you know, Avaya has had a great number of products over the years, and to make it easier to find the lifecycle information that you are looking for, I recently pulled all the data together that I could find and released a new consolidated lifecycle matrix.

This document contains product lifecycle information dating back almost 15 years. For any given product, you can see the lifecycle dates and announcements, as well as search by material code.

To read more details on this topic, please reference the official Avaya Product Lifecycle Policy here.

I hope this clears up some questions you might have had about our product lifecycle.

If not, please leave questions and comments below. I will also be attending and speaking at the IAUG and PCC conferences in Dallas April 27th through May 1st, so feel free to ask me more questions in person.

Contact or follow me on Twitter at @CarlKnerr.