Components in non IT assets
Before we spend a lot of time settings things up incorrectly, can I check how others are using this part of SD+ please?
We have a number of telephone phone systems installed at our clients' premises. The systems normally consist of two items; the phone switch and the voicemail Each of those items have been created as separate assets.
Inside each of these items are various combinations of cards, line cards, extension cards etc.. The we have created as components.
The phone switch is say called London phone switch, it has an ISDN line card, which is a component which we have given the name London ISDN card.
When we look at the asset, the component section contains the cards, but the names of these cards are all prefixed with London (or whatever we have chosen). Do we actually have to make the card names unique? Are we going to hit problems later and lose the identity of the components if we don't follow this format e.g. London and Manchester's ISDN cards could both be called "ISDN CARD"?
Our preference would be to ID the cards for tracking but maybe do it through the serial/asset numbers.
Final questions, when attaching the asset to the user can we a) have the list alphabetically sorted and b) be able to allocate an asset to a case even if the requester isn't normally associated with it, i.e. a user "FRED" may report a problem with the London phone switch, but it is normally associated with a user "LONDON - SITE ".
We want to be able to track the case against "FRED" as the requester, LONDON-SWITCH as the asset even if it is associated with "LONDON-SITE".
I hope that makes sense?
We have a number of telephone phone systems installed at our clients' premises. The systems normally consist of two items; the phone switch and the voicemail Each of those items have been created as separate assets.
Inside each of these items are various combinations of cards, line cards, extension cards etc.. The we have created as components.
The phone switch is say called London phone switch, it has an ISDN line card, which is a component which we have given the name London ISDN card.
When we look at the asset, the component section contains the cards, but the names of these cards are all prefixed with London (or whatever we have chosen). Do we actually have to make the card names unique? Are we going to hit problems later and lose the identity of the components if we don't follow this format e.g. London and Manchester's ISDN cards could both be called "ISDN CARD"?
Our preference would be to ID the cards for tracking but maybe do it through the serial/asset numbers.
Final questions, when attaching the asset to the user can we a) have the list alphabetically sorted and b) be able to allocate an asset to a case even if the requester isn't normally associated with it, i.e. a user "FRED" may report a problem with the London phone switch, but it is normally associated with a user "LONDON - SITE ".
We want to be able to track the case against "FRED" as the requester, LONDON-SWITCH as the asset even if it is associated with "LONDON-SITE".
I hope that makes sense?