Originally posted by smardaz:
Originally posted by Cory:
Originally posted by smardaz:
I guess I should have mentioned that I am implementing a inventory software. I will created a bar code for each item for purposes of knowing what we have in the storeroom as far as item counts, once a piece of hardware leaves the storeroom it is tracked in another program |
INTEGRATE!!! This would be the time to make that happen. Huge ROI opportunity. |
Not sure thats possible Cory, it's our break/fix and request ticketing software and if I was to try and use that I would have to involve CA Technologies which is the vendor for that. This is a piece of software that is a one time $1500 multi user fee which as you probably know is a paltry sum in the world of corporate licenses.
Our problem that needs fixing really boils down to this: If a big-wig were to walk in here and say "hey Jason, how many Dell desktop pc's do we have in here?" I would have to reply "um I dunno, let's go count"
But if that same person wanted to know how many and what kinds of pc's were deployed system wide we could pull an SCCM report and tell them almost instantly. |
It sounds like the RFID tags/barcodes can be standardized between systems, but outside of that you're right about the costs of such an integration being wildly out of budget.
I'd suggest an obsoletion check be added on your re-inventory process - preferably before system check-in, it's a nice little process optimization that comes to mind.
I guess that's what I would suggest in general, is to use this opportunity to look at your processes and reevaluate them where necessary. I'd do that by familiarizing myself with the software, then matching your protocol up to the reality of the software and situation. That methodology should ensure that your process won't be borked by software that doesn't do what you think it should do. (more common that you'd expect)
I am available by PM if you have any specific questions, no fee, because DPC. :) |
