So you already know how to best utilize software asset management (SAM) and maintain the system, but what should be expected to be seen in a process map? In a post at his blog, Joe the IT Guy charts out the elements of the process map in addition to elaborating on their relevance.
Become a Cartographer
As part of the ARIS modeling framework, there are multiple items to help guide the process and in this post, there are twelve of importance. “System Used” helps to provide clarity to stakeholders that a portion of the software is used in the execution of the function step. “Data” elaborates on which inputs and outputs are important, how the data has changed through the process, and when it underwent this change. “Trigger” indicates to a person why a function step is essential. “Risk” indicates to stakeholders the issues of which they should be made aware. A “Measurement Point” is added to the process map at a point in which a metric can be analyzed for its performance. The “Process Interface” helps to model entry and exit points; however, keep in mind that a process can have many points of entry or exit. These are but a few items of interest.
A simple suggestion is to not make the process maps too long; they should be able to satisfy both major and minor process goals without overcomplicating anything. So what do these major and minor objectives look like in a SAM process? A major objective, simply put, would be to effectively and efficiently request software, while still staying in line with the company’s licensing. Minor objectives include: line management endorsement of the project, technical endorsement, or a license check before any requests are implemented. Not all of these objectives are required for every project, but they do offer a guiding light to the process.
You can read the original post here: http://www.joetheitguy.com/2015/10/20/write-software-asset-management-process-part-2/