|
BC13 release active No additional license purchases available |
| MX-One TSE |
|
Version 4 X active |
Licensing has been around since the introduction of BC10 software on MD110. There is often confusion surrounding what you can and cannot do and who can do what. We are outlining some clarifications on licensing with regard to the products you own and retain the right to use (RTU). Licenses do not expire as such, but they are phased out in accordance with the vendors product roadmap management. In those cases upgrades are offered to customers.
The biggest issue that is reported is that users who want to add licenses after a version has been phased out are unable to expand on their present version and find it necessary to upgrade. Anyone on BC12 or previous versions are in that position. It is not a concern from a maintenance perspective but if growth and additional functionality required and upgrade to BC13 (MX-One TSW) required.
Always check you know the active lifecycle of a license you are purchasing.
With a movement towards software based solutions vendors are focusing on similar models to the IT world in order to provide ongoing revenue streams.
Software assurance is an option that should be offered via your service provider who will then set up the necessary agreement with the vendor(Aastra). It is vendor initiated offering.
But what is it and and what is different about it and a standard maintenance agreement?
Our interpretation is that bug fixes are part of a standard maintenance contract; software assurance is a time bound upgrade contract. In other words you sign up for a fixed forward period (1-3 yrs typically) to give you access to the new releases of software at a 'discounted' price.
We would encourage you to discuss your maintenance / support needs with your service supplier in order to understand what options you have going forward.
TIP... make sure you are aware of the entire cost ( i.e. cost of implementation from the service provider).
Last brochure (circa dec 2009) on licensing that explains the software assurance offer. (brochure).
All we can recommend is that you make sure you are fully aware of what you are being offered (i.e. upgrade project costs are normally not included) and if entering a time bounded offer for upgrades, vendor/supplier delays should be reflected in that agreement appropriately.
Remember back in 2008 Ericsson originally made a mess of introducing software assurance. The user group sent them aware to try harder, unfortunately some 3 years on with Aastra and the software assurance subject is still one surrounded in some mystery. You basically have to have software assurance today to purchase an upgrade... so where is the choice and what are you getting for the money? Perhaps the biggest ongoing issue is, you are buying an 'assurance' over a fixed period of time but the vendor does not commit their portfolio releases to a time frame.... a leap of faith required?
Hopefully Aastra will be able to clear up the outstanding issues, we will continue to press for it!