Allow a component to be assigned to a person as well as asset

Allow a component to be assigned to a person as well as asset

At present the component element can only be assigned to an asset which in the majority of cases makes sense, as it should be a building block element of an asset.
However we have the situation whereby we will allocate component items ( Mice , Keyboards etc ) to contract staff who don't have a PC etc ( defined asset ) to assign the item to.

This leaves us with an incomplete inventory of the components. I guess a dummy asset could be created, but that then adds to the licences count, and the only reason for the asset existing is to make a link to a person.

I also don't want to have to create an alternative asset category for 'Mice-assets' to record the physical mouse as an asset and then allocate that. Doing that would mean there would be no single view of 'Mice' for instance, and when a mouse arrives into the storage area we don't know if it is going to be used as a standard replacement or loaned to a non asset bearing member of staff.

Possibly the provision/differentiation of components and assets could be moved down to physical asset level indicating that each specific instance is either to be treated as an asset or a component, whilst retaining a single product type.

                  New to ADSelfService Plus?