

#Request a software carbonate license
At this point, function step 1.30 could also be called into action as a result of a change management request being rejected over any number of issues other than whether a license is in place. If the request is rejected, then the requestee is informed with the reason why.

This process is initiated by one of three ways either a request is raised by an end user in a standard fashion, or in performing due-diligence in checking for Named User Licenses the SAM Manager needs to go through the approval process to buy extra Named User Licenses, or finally because a Change Management Request has been made for which there are no licenses left.Īt 1.20, the Line Manager to the Requestee is tasked with either approving or rejecting the request.
#Request a software carbonate manual
manual steps) increasingly the SAM marketplace is looking to automate the request process with products such as Shopping by 1E or App Portal by Flexera. You may have noticed that all of the steps modelled so far have been with rounded corners (i.e. The trick with process engineering (like programming) is to focus on one element, get it working (and get it working well) and then consider pulling in other elements at a later stage – try not to map the moon! I suspect the reason many folks get in such a bind with designing a process to handle software requests is that they try and bundle no end of steps into the overall process, including procurement, testing, deployment etc.
