How much information do you think you need to justify increasing/decreasing license totals for your crucial and expensive Engineering Tools?
Some companies decide to move forward with in house scripts which is normally tied to when a sole individual and others have nothing in place. We have spoken with many IT Professionals who all state that when it comes to the management of their Engineering Tools, in house scripts are useful but extremely time consuming. In situations where there is nothing in place to manage engineering tools, IT solely takes on a reactionary role.
Many organizations needed to change behavior and redirect project efforts. ESAM / ESAO (engineering software asset management and engineering software asset optimization) needed to be put on hold in favor of implementing and managing remote office infrastructure and security.
As increasingly more people are working remotely, there is a greater emphasis on eSAM/eSAO, compliance and auditing as part of the remote office strategy.
However, servers may go down and thus cause issues. As an example, on Wed. Nov. 25th, when AWS went down in North America, it actually actually knocked out several 1000s of services, such as Adobe and others. This has stopped people from using Autodesk products or making it difficult for them to login. Named user and subscription users are all down or struggling to get a license.
Does your company use in-house scripts or no solution in place? Start being proactive about your engineering licenses and gain organization, oversight and minimize time consumption with LAMUM. With LAMUM, you can follow best practices for engineering license management and monitoring. LAMUM (License Asset Manager with Usage Monitoring) is an innovative and best in class suite that helps you leverage your data to properly identify contention of licenses, the need to increase/decrease licenses and ability to alert of denials. LAMUM delivers an organizational structure with oversight to make data driven decisions on what, when and how your expensive engineering tools are being used.
One thought on “Rethinking eSAM & eSAO Strategy”