Service parts inventory
We are thinking about migrating from an internal help desk system to the K1000 Service Desk. One of the functions of our existing help desk is a parts inventory. When a technician services a machine and it needs a part, it can be added to the ticket, via the inventory by the owne,r and deducted from available parts. Is this possible with the k1000? Any help is appreciated.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
airwolf
13 years ago
Posted by:
GillySpy
13 years ago
Thinking out loud:
So you would likely have a custom field whose contents is a list of available parts. You could have as part of that list a Serial number or a separate field for the serial number of the part.
A rule could detect your part selection and mark the specific part assigned as unavailable as well as mark which ticket it is tied to. You could have separate reports (or asset view)on how many parts are available.
This is not trivial stuff though
You would need some rules that handle a situation where the same part has been assigned to multiple tickets and flag it. Probably want to award it to the first save.
So you would likely have a custom field whose contents is a list of available parts. You could have as part of that list a Serial number or a separate field for the serial number of the part.
A rule could detect your part selection and mark the specific part assigned as unavailable as well as mark which ticket it is tied to. You could have separate reports (or asset view)on how many parts are available.
This is not trivial stuff though
You would need some rules that handle a situation where the same part has been assigned to multiple tickets and flag it. Probably want to award it to the first save.
Posted by:
tomssd
13 years ago
Posted by:
GillySpy
13 years ago
I had envisioned that if you have 10 widgets then you would have an asset type called widget and 10 assets of that type with 10 different serial numbers. however...if you do not individual serial numbers then it gets a bit trickier. You would likely have one asset of that type with a field called quantity. You would have to have a rule to adjusts the quantity as parts are used. To ensure that no parts are double counted you would have to report against the totals and adjust OR have a list of tickets within the asset. If a ticket can use up more than one item then you'll have to have a quantity field in the ticket.
Parts of this type (ie with no serial number) are usually of lower value and it's not the end of the world if quantities are slightly off for a period of time. You should have a periodic inventory process that checks the real number against a report for quality assurance
Parts of this type (ie with no serial number) are usually of lower value and it's not the end of the world if quantities are slightly off for a period of time. You should have a periodic inventory process that checks the real number against a report for quality assurance
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.