thanks the info.
This will be a helpful guideline to follow.
BTW, I like your analogy.
I think this would apply to most tools.
"Beal, Weston" wrote:
> A SI simulator is like a cake. A top quality cake is very good on the
> inside and then is nicely decorated on the outside. A Styrofoam cylinder
> covered with icing is not very filling and a moist, luscious chocolate cake
> covered with dog crap is little value. The cake is like the simulation
> engine and of course the decoration is the user interface.
> I would say that the simulation engine is the most important. Here are some
> points I would look at:
> - Does the simulator support your latest models? Is the company very
> committed to support the latest modeling technology in the future? Models
> are and will be the most important factor in SI simulation.
> - Does the simulator have an adequate internal model for transmission
> lines? Ideal lossless lines are generally not good enough any more.
> - Can you get accurate results of a system simulation in a reasonable
> (defined by each customer) time? Obviously, you wouldn't run a SPICE
> simulation on every net in your multi-board server design. My favorite
> simulator just takes too long to do crosstalk, so we don't do much of that.
> - Is the user interface intuitive enough for those who will use it?
> Hyperlynx Linesim is good for beginners while you need a few months to
> figure out how to efficiently run Viewlogic XTK.
> - I would also try to see the advancement of a tool over the past year
> or two. Every tool I've seen has holes in it and I'd like to see who is
> filling the holes that fastest.
> - Try to guage post-purchase support. Ask the vendor what their
> commitment is, but then ask some customers (SI list) what their experience
> has been.
> There's a lot more to look at but I don't have all day to write. I hope
> this will get you thinking about some things that you hadn't thought of
> Weston Beal
> -----Original Message-----
> From: Daniel Roganti [mailto:email@example.com]
> Sent: Tuesday, 05 October, 1999 9:30 AM
> To: firstname.lastname@example.org
> Subject: [SI-LIST] : Features to look for in an SI
> << File: Card for Daniel Roganti >> Hello,
> I'm beginning to evaluate a SI Tool and to arrange a Demo
> using our existing project.
> Would anyone have some insight into what important features
> to look for in an SI Tool.
> I'm trying to differentiate between the nice-to-have and
> really-need features.
> Any info is appreciated.
> Daniel Roganti
> **** To unsubscribe from si-list: send e-mail to email@example.com. In the BODY of message put: UNSUBSCRIBE si-list, for more help, put HELP. si-list archives are accessible at http://www.qsl.net/wb6tpu/si-list ****
Content-Type: text/x-vcard; charset=us-ascii;
Content-Description: Card for Daniel Roganti
org:Optical Networking Group<IMG SRC="http://www.euronet.nl/users/ragman/internet/gifanim/lucent_orbit-anim.gif" HEIGHT=75 WIDTH=97>;Network Multiplex Labs 3
adr:;;Botterstraat 45;Huizen ;;1270AA;The Netherlands
title:Hardware Design Engineer
**** To unsubscribe from si-list: send e-mail to firstname.lastname@example.org. In the BODY of message put: UNSUBSCRIBE si-list, for more help, put HELP. si-list archives are accessible at http://www.qsl.net/wb6tpu/si-list ****