Good Morning All,
This post may be a long so with respect to those that do not wish to read all the way through only to find out what I was on about was of no interest, the main theme is: I am curious about VC/Shark's user base. How many users, where located (generally) geographically, what industries/products is VC/Shark used for mostly and what is the future plan...continue as is or being groomed for acquisition?
I have been in the CAD business for over 30 years and still am a current Creo and SolidWorks user. Over that 30 year time-frame, I have worked in a number of industries relating to product design, product and industrial engineering and industrial design utilizing a number of software. The list of software I have worked on (from oldest to newest ((some used simultaneously)) are: Applicon Bravo, ACAD, Intergraph I/EMS, CADAM, PDGS, Catia V4 and V5, Creo(Pro/E), ICEM/Surf, SolidWorks and now I am learning VC/Shark. I do not list these to brag. I list these because, upon seeing VC/Shark's capability vs. price, I knew it was a wise purchase, no doubt. However, I am curious as to the long term wisdom of my learning Shark relative to future work opportunities. In other words, just how "marketable", known and/or in demand is VC/Shark? If I am going to use the remaining limited time of my life to learn a software, I would like to have some comfort of knowing it will pay off somewhat in the end.
What is a typical VC/Shark like? Single, independent designer/user or multiple user CAD group? Are there any companies standarized on VC/Shark that you know?
Where, globally, is VC/Shark utilized most? Is it used mostly in North America, EU or a diverse user base?
What are the industries that "know" of VC/Shark? Building Trades/Architecture, Ship building, etc???
Is VC/Shark (Tim, I guess?) building/maintaining/updating VC/Shark to make it attractive for sale, like SolidWorks did with Dassault? I mean if VC/Shark gets gobbled up (pun intended) by one of the bigger fish, it runs the risk of getting stagnated and allowed to die on the vine. BTW....a bit of history. When Mike Payne left PTC and started SolidWorks, the rumor on the street was he had always intended to "sell" big. He knew capitalizing on Windows based architecture instead of mainframe was the "hook" and played that brilliantly. $310 million brilliant ways in fact. That is off point... The point is when SW sold to Dassault, everyone up top intended to let SW languish in the back room (which it did somewhat from roughly 1997-2000) so as not to cobble sales from Catia. (Dassault did this with ICEM/Surf too somewhat). But because of SW's brilliant guerrilla marketing efforts early on (colleges, disgruntled Pro/E and Catia users) pure loud voices demanded SW stay relevant, and it has for a long time. To use some automotive parlance, Dassault has been in the uncomfortable position of making certain their Camaro SS (SolidWorks) cannot outrun its Corvette ZR1 (Catia) in a drag race. Although knowing both V5 and SW, I can attest that they are very close to one another. In other words, a CAD Rockstar, whether SolidWorks, V5 or Creo for that matter, will arrive at the finish line very close to one another. So, in your opinion, what is the future of VC/Shark? Will it stay somewhat where it is with updates to core functions or will it gain in functionality over time?
Was there ever a push for an Assembly mode in VC/Shark history? I find one of the difficulties in VC/Shark is "managing" everything by layers in the multi-body environment. Added to that, the fact that multiple selection (I.E. selecting more than one layer at a time with the Shift or CNTL key) is not possible in the layer tree, and that for some users the scroll wheel does not work all the time, makes for a VERY long day when the "model" gets to be over 7 "parts". I am curious as I see the addition of something like a functional Assembly Mode would add to the power/usability of VC/Shark. I fully concede there is much more I need to learn about VC/Shark. All software are usually much deeper and much more capable than a two month Noob like myself knows. Maybe some of what I say will be useful is already "in here". I look forward to learning it if that is the case.
In the end, I have enjoyed the learning curve of VC/Shark so far. Lots of capability and the user interface is decent with a lot of "niceties". BTW, Tim if you happen to be reading this, did you have any history with Intergraph I/EMS of the 1980's? VC/Shark reminds me of it very much from the way models are constructed (although this is common with explicit boolean CAD) to the data management, to flattening views on drawings, on and on. As I learn VC/Shark I find myself transported back a few decades asking very familiar questions! :o) I do not say this to be disparaging at all. I say it with respectful admiration that VC/Shark is a powerful as it is and has a following. Nicely done!
Have a great weekend all. And if you made to this point, thanks for reading it.
Dean