DRAFT DRAFT DRAFT NOT VALIDATED.

(tentatively we will finalize these minutes in the week of the 25th of October)

Presents

Michal Kwiatek <Michal.Kwiatek@cern.ch>; Siavas Firoozbakht <siavas.firoozbakht@cern.ch>; Aleksandra Wardzinska <Aleksandra.Wardzinska@cern.ch>; Paolo Tedesco <Paolo.Tedesco@cern.ch>; Vincent Brillault <vincent.brillault@cern.ch>; Alessandro Di Girolamo <Alessandro.Di.Girolamo@cern.ch>

The topic: how can we integrate the Microsoft products in the Eligibility Framework - which are the processes we need.

Interesting and intense discussion, at the level of a brainstorming. 

Summary: the new resource portal (NRP) will be the entry point from where a user will be able to see if he/she is eligible, eligible under guarantor approval, not eligible for each resource. For e.g. MS product, the eligibile ones should be able to click and "subscribe". The non eligible ones, should see that they are not eligible, with link to the relevant admin eguide.

For the eligible under guarantor approval are the issues.

• we all agreed that we believe that "guarantor" in the case of resources which needs a license (eg. MS, adobe, cad, jira and many others) should be seen as "the budget holder", i.e. the person that can guarantee that this person can have that product, and the guarantee is that the guarantor put a budget code for that user.
• how do we handle "multiple requests": e.g. FCC comes and need to have the license for 50 persons. Should there be one doc per person? Does not look effective.
• Microsoft service managers "needs" the list of persons with the relative budget code, so that, in case is needed, they can invoice the cost. --> this is clear and agreed that is reasonable and should be part of the solution we are still looking for.
• we agreed that we cannot measure days of the license, i.e. if a user ask through a guarantor a license and (in whatever way) this will be agreed, then even if after one week the user leave, the cost is for the full year.
• we discussed the concrete tool to use. From the NRP there could be links on what to do, and the to do could be to ask his/her guarantor to create a specific RP appriopriately done for that resources, which should be filled by the guarantor and then the Service Desk (SD) could add the person in the appropriate group.
• we discussed EDH and Record Producer. It took a while (to Ale) to see that actually a RP will trigger a TID and an EDH, i.e. we could think directly also about creating an EDH.
• we discussed the "cost" of this RP, someone that by hand need to take the RP, create the TID and then the EDH (which can then have the workflows with the appropriate signatory persons): it's going to be very difficult to understand the balance between having too many of these and just grant the resources, e.g. for a license that cost a few tens of chf/year won't make sense, but again if we do have hundreds of these we should track them.
• we agreed we need to think more
• we mentioned but did not discuss the open point of the Microsoft users, for which we do have some 2k licenses that are provided on non-eligible users. This is another important points that will require discussion on how to handle it.
•