To: Dr. J who wrote (11944 ) 2/25/1998 10:33:00 AM From: Steve Sanchez Respond to of 31646
posted this a while back: From: Jim Lynch <jjplynch@nospam.aol.com> Date: 1998/02/06 Message-ID: <34DB9607.69AA@nospam.aol.com> Newsgroups: comp.software.year-2000 [More Headers] Tina Vince wrote: > I suspect that, given that _everything needs to be inventoried, > and all have distinct components/features, I will probably have to > settle for more than 1 tool/repository. > > I do not profess to be an inventory/asset management expert > ...not by a longshot. However, I have to come up with evaluation > criteria or a scoring matrix for selection of the appropriate tool. > Can anybody offer any suggestions? I've been working on inventory and tracking for a while now. I notice that quality of data is a big thing. A couple of the issues I've had, are incomplete data, a reluctance to work on it until the first of the year (now passed) and no easy way to link components of a system. Now, that's mostly embedded systems I'm talking about. PC/Network issues are really just being addresses. Manufacturing Production Systems are often some combination of PCs, microcontrollers, PLCs and various instrumentation and associated software. Ensuring some linkage between these "sub-projects" is beneficial. I was favorably impressed by the Database tool that TAVA Technologies had. If we hadn't completed most of the inventory by the time it came to market, I would have strongly recommended it. It permits you to describe your entire system by component (down to the chips). And they'll take your data and analyze it against their growing DB of compliancy information. Of course, it doesn't come cheap, but that is a business issue. Jim steve