KollabNet SolidMap at SWW

Feb 09, 2007 4 Replies

Did anyone check out KollabNet's SolidMap, which was at SWW? It's the addin that gives you block diagrams showing relationships between parts and features. I'm nearly positive that we have designed in circular references, but we're either too lazy, too stupid, or in too much of a hurry to find them. (Naturally, I claim it is the latter.)


Jerry Steiger Tripod Data Systems "take the garbage out, dear"


"Jerry Steiger" wrote in news:532eljF1qo7dbU1 @mid.individual.net:

I haven't seen it in action, but...

This or something like it really really needs to be integrated into SW a la CimLogic Hole Wizard. I'm a bit skeptical that it can save the reported 31% of time spent with SW, but it would be a huge help to understanding and maintaining relationships in models.

Initial cost is rather steep...

I looked at it there, and it seemed to work pretty well, and made cool pictures, and they had a show price of only $165 or so, but I don't see that I would use it that much. If I get a tree that lights up, I usually uncover it fairly quickly. Maybe a nice tool for someone that is always working with someone else's stuff that is having problems. I am going to go through the demo cd I got, though.

WT

I ended up buying a show special seat for $150. I can see value for seeing the structure of data sets you are unfamiliar with. I also see it as a training tool to help our engineers understand the rat's nests of relationships that they like to build on occasion. The visual picture of what they have for relationships may get a few light bulbs turned on. Is it worth $650 plus maintenance a seat to have on everyone's computer. I do not know.

I plan to install it next week on my machine and give it a test drive. I will report my findings after I test the package for a week or two.

Regards,

Anna Wood

formatting link

A while back I answered their survey and they sent me a nifty alarm clock / thermometer. This is a take off on dyna-bits old program. I wrote a much simpler version as a macro. My thinking is that at least one user in every installation should have something like this to sort out legacy or problematic parts. As I recall it didn't answer the question that really needs answering, " Which features will be deleted if I delete this parent?"

TOP

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required