Perpetual Software with SMA version upgrade (no subscription dates)

Lyn asked a question.

July 9, 2018 at 7:00 AM

I need to add software to Snow, but am not sure of the best way to record this one. We have purchased software which has a perpetual licence, but we have also purchased a SMA for 2 upgrades. The SMA therefore doesn't have a time/date period, but will expire once we have used the second upgrade. I'm very new at Snow, so could be something very obvious, but everything I've tried is asking me to enter a subscription date, when there isn't one. Thanks in advance.

Software & License Management

Lyn
8 years ago
Thank you both for your replies. You're correct, it is odd that a time period isn't specified. The reseller has confirmed that there is no time limit, but I think I will try to clarify this again directly with the vendor. Thanks again for your assistance. Much appreciated.
Expand Post
ScouseSAM
8 years ago
Hi Lyn, I'm with ?, it would be very unusual for a vendor to not impose a period against your SMA. The "2 upgrades" is likely to mean, the next 2 releases but without knowing your agreement, I really wouldn't want to speculate too much. The only automatic expiration method in Snow is by date as far as I'm aware. If the vendor is very typical in their naming conventions, "App1, App2, App3" then thinking outside the box you could blacklist the version above what your SMA would entitle you to. At least that way you'll be aware of any breach and be able to remedy the situation quickly. But yeah, I think Mike has the right of it. If it were me I would seek clarification in the SMA documentation or contact the vendor directly because it sounds like your SMA is good for the next 2 upgrades. Knowing this you can estimate dates as Mike suggested and change accordingly, using the Notes field in the maintenance support tab you can add in there about your entitlement to 2 upgrades.
Expand Post
Mike Rossouw (Flexera Software)
8 years ago
Hi Lyn, In my experience, vendor agreements will dictate a finite term within which you can claim and or activate the specified number of upgrades. Another way to look at this is most product vendors aim towards releasing at least 1 major version of their software per year, so depending on the vendors specific road map and release cycles, if it turns out they do tend to release more than one major version per year then look at setting a 1 year agreement period. Alternatively, you could set your agreement period to support two major releases over the two years. There isnt a way that I am aware of currently to control the number of upgrades other than controlling or overriding the agreement periods in line with the release cycles. So the approach in this case would be to: Identify from the agreement terms (small print) or by liaising with either your supplier or the vendor themselves to establish what that upgrade period is. If there is a stipulated term then create your agreement using the standard software agreement creation method with the start and end dates in line with the agreement period. If no period is stipulated then refer to the vendors release cycles to establish an agreement period in which upgrades will likely occur. add sufficient notes and alerts to remind yourself and other Snow users of the limitations and reasons the agreement is setup the eay it is. I hope this helps
Expand Post

Related Product Forums