

Historical license usage is only an indication of future use, but should give a good approximation of the most heavily-used software, such as AutoCAD Civil and AutoCAD Vault for a civil engineering company.


When deciding whether to move to Token-Flex or remain with the status quo, the user organization needs to estimate its expected token usage over the contract period. While a distributed server model is supported, a redundant server model is not. Many multinational enterprises will have a distributed license server model due to business continuity, maintenance and availability considerations. This is because the 24-hour usage period is linked to the license server location.
Autodesk flame review software#
For instance, if the license server is based in the United States and the software is being checked out in Singapore, with a 12-hour time difference, or in Seoul with a 14 hour difference, the token usage could double up. Location is another factor that contributes to the costing model. The actual cost per token is negotiated at contract signing the unit price is tiered, based on number of tokens purchased, with discounting options on large quantities. Because tokens are allocated per user for a particular product, a single user has the ability to fire up several instances of the software on different machines, while only paying the daily token price once, i.e. The user starts the transaction by withdrawing a certain number of tokens, which gives him the ability to book out the software required. The token price tends to be higher for more specialized tools for instance AutoCAD MEP and Revit MEP will have a higher token price than plain old AutoCAD, which ‘costs’ 6 tokens per day currently. As with the annual tokens, any unused tokens will expire at the end of the term.Įach product in the customer’s portfolio has a fixed token “price”, which is generally based on 24 hours of use per user. Contract-based tokens, which last for the term of the contract, say three years.Annual tokens, which expire after 365 days if unused.After the products are chosen, the customer purchases tokens to run them. Token-Flex works strictly on a per-product basis and does not include suites. The allocation of licenses is set to 9,999 although this has no real value because pricing is now based on usage rather than number of licenses. The customer is then provided with access to the software they require from AutoDesk’s stable. Token-Flex Licensing is a fixed-term contract, the expiry date of which can vary from two to five years, based on an agreement between the customer and Autodesk. While using consumption as a foundation for licensing costs is an interesting model, some users like to do some planning and estimation before moving from their perpetual or other current licensing model. Autodesk has a licensing option based on actual usage, targeted at their enterprise customers, called Token-Flex. Over the last year, there has been a steady move from the traditional models of licensing by site, number of concurrent users or number of licenses to consumption-based licensing, or “pay-as-you-go” licensing as it is commonly known.
