We have pre-defined criteria regarding the critical level of any request that would be logged for assets. The definition of the Critical level depends upon the Job Title of the Requester with whom the asset is attached and is used by him. Requests logged for assets attached to users with Job Title above a particular level in the Organisation would always have Critical Level I, whereas Requests logged for assets attached to Requesters below that level would always have Critical Level II.

If an asset is shifted from a Requester having Critical Level I to another Requester having Critical Level II, then all Requests for that asset would always have Critical Level II and vise versa.

 

For example, a request generated for assets (For example asset ids A6, H2, L1) used by particular predesignated requesters (For example Requester A, B, H respectively) would always be under Critical level I, whereas requests logged for assets (For example asset ids B5, T2, P8, B3) related to/ used by few other predesignated requesters (For example D, G, N,S respectively ) would always have Critical Level II.

If an asset H2 which was earlier used by Requester B is shifted and is now attached to Requester N, then subsequent to the attaching of the asset with Requester N , all requests generated for the asset H2 would have Critical Level II.

 

Please advise if it is possible to configure the CMDB/ Asset Relationship or otherwise so that the Request for the assets has the Critical Level automatically defined depending upon the Requester's Job Title and the assets used by him.