In the world of Software Asset Management, engineering applications are often overlooked—sometimes due to a lack of resources, missing licensing expertise, or the absence of ‘know-how.’ Other times, they are managed solely by internal engineering team members.
In this article, let’s explore why Software Asset Management (SAM) must extend beyond business applications. This perspective is based on my experience, and I’d love to hear your thoughts and feedback!
Great insights and totally agree. In my past roles the areas of engineering, niche, specialty or otherwise became a separate focus due to their low deployment yet extremely high cost per user, device and so forth. Unlike mainstream business applications where we might own, with ability to charge back, harvest to optimize the area of the specialty software however was owned by the consuming org’s yet we provide the centralized SAM oversights to conduct optimization efforts to ensure costs were held in line, through contract reviews, usage, and other such action via specialized SAM tools, policy and process to achieve the end goal.