An important benefit of proactive software asset management is making certain you are leveraging and maximizing use of your latest technology.Before transitioning every user to Creative Cloud, you should utilize the software metering capability of your SAM tool to evaluate what Adobe products are deployed, where they are deployed, who is using them, and how often they are being used. Any time your organization makes a technology change it’s an opportunity to review the current state of deployed assets and their related purchase agreements to ensure you are using what you pay for — and only paying for what you use. Adobe’s new Creative Cloud offering represents one such opportunity.
Adobe Creative Cloud is not a pure-play “cloud” solution, as the software is deployed on-premise with cloud collaboration and management features. Therefore, it is possible to use software asset management tools to track the inventory and usage of these discrete deployments and marry them up with their associated licensing agreement(s). By doing this, you will likely find a number of users who have the full Adobe Creative Suite on their PCs, but only occasionally utilize one component.
Uncovering this information will enable you to consider two courses of action:
- Refrain from transitioning these users to Adobe Creative Cloud and avoid making an unnecessary purchase.
- Get more out of the initial investment by training the users on Adobe Creative Suite so they can be more effective using the product.
At the end of this process the organization will know how many users should be transitioned to Adobe Creative Cloud as well as any skill gaps that will need be to be addressed to ensure they maximize their investment and leverage the full functionality, while avoiding unnecessary spending.
Additionally, it is important to review the license agreements the organization currently has in place with Adobe. Licensing may have accumulated over time and there is likely an opportunity to consolidate into one agreement, drive down cost, and simplify management going forward.
Finally, one of the latest developments in this area is the November 2009 publication of ISO/IEC 19770-2 Software Identification Tags, which allows publishers to “tag” software so it can be easily identified on the desktop, and ultimately managed as a deployed asset. Adobe began tagging its software with the release of Creative Suite 4, so it’s possible to use these tags to differentiate between on-premise Adobe Creative Suite applications and Creative Cloud variants of these applications. (However, it’s important to be aware of the limitations of using tags in isolation for identification of Adobe products.)
Once you’ve performed a review of your Creative Suite utilization, you will be ready for your new journey with Adobe Creative Cloud and in a position to be smart about your migration, while maximizing your organization’s investment.