Archive

Posts Tagged ‘synchronous’

My meeting with Siemens PLM

October 6th, 2008 10 comments

Earlier this year I had contacted Siemens PLM about getting an evaluation copy of Solid Edge with the goal of exploring the possibility of writing a book on it. I checked some of the Amazon stats, and it seemed that the current Solid Edge books were again mostly step-by-step tutorials for beginners written by educators. The book sales for Solid Edge books were in general well below those for SW books, presumably because there are fewer users.

Siemens PLM marketing people got back to me, seeming somewhat more guarded than the Autodesk folks who just sent me a copy of Inventor with little if any discussion. Siemens told me that they were just about to release a new version of the software, and that any effort should be postponed until after the new software was out. This was before news of Synchronous Technology hit the web.

Once the ST hype started hitting, and it was clear that this was at least going to try to compete with both SolidWorks and the likes of Spaceclaim, a firestorm of speculation was set off. There was precious little real information. All that existed were some overblown marketing statements, and a whole lot of copies of the marketing materials from everyone’s favorite (and unnamed) CAD terrorist. If this was really new, I wanted to know what it was. As time passed, there were few people who had really used the software stepping up to say anything beyond the marketing hype.

So in my curiosity, there seemed to be only one way to draw out people who actually knew what was going on. Of course. I posted my own ridiculous conjecture. Looking back most of it was factually incorrect, because I had no facts to go on, but as time went on, people from Siemens started to comment, and they started to give some actual information.

In the end, I still didn’t have a very good idea about the details of what ST was or how it worked. I couldn’t answer the question about if users would like it or find it useable because those are the kinds of things you can only tell by actually using the software. CAD terrorists and self proclaimed really smart guys were saying similar things, as far as I could tell based solely on marketing materials. Sounded like a bad idea to me.

After the release of the software when actual users had the software installed, things seemed to get quiet. It didn’t seem to be a good sign for the software when users have it in their hands and they aren’t saying anything about it.

A couple of weeks ago, I got a call back from the Siemens marketing people. They wanted me to come down to Huntsville and talk to them about the software, get some training, and take the software back with me. It seems they contacted a few other SW bloggers as well, but I was the only one who accepted. One of the benefits of being independent is schedule flexibility. A separate event was held for members of the press.

Part of the “problem” is that Solid Edge doesn’t have more than a few bloggers that cover the product. This blog seems to have given SEwST more exposure than any other. Most of my coverage was simply out of curiosity. Another part of the problem is that many people have the perception that Solid Edge has not been marketed with much conviction, possibly because if its seemingly jealous relationship with NX. So now that Solid Edge users have something to crow about, they want to crow.

My visit to Huntsville involved a number of people. Most of the time was spent with Mark and Doug, internal corporate training guys who usually train reseller AEs. To begin and end the day, there were as many as 8 of us around the big conference table. Dora Smith of marketing was my main contact. Kris Kasprzak of marketing was also there. Bruce Bose also of marketing was a fellow Rochesterian and RIT alumn. Dan Staples is the director of development for Solid Edge and has commented on this blog a few times. Mark Thompson and Doug Stainbrook were the internal trainers. Mark Burhop, keeps a blog. Mark and Dora can be seen on Twitter.

The questions went back and forth. They had as many for me as I had for them. In the end, they did a great job of showing me the software and answering my conceptual questions as well as they could.

I’ve got a magazine article in the works, and if it gets published, most of the content about the software is in that article. The logistics on the article may fall through, or another venue may open up, so I’m not going to get into the software in depth right here right now.

One thing is clear, though. The guys from Siemens really believe that this product is going to replace history-based modeling. There is none of the Spaceclaim equivocation where the two technologies can coexist side by side. Dan Staples said “Ten years from now history based modeling will not exist”.

Categories: CAD Commentary Tags:

What can you learn about CAD from blog statistics?

August 12th, 2008 3 comments

The first thing I learn is that I should be writing a Solid Edge blog. If I do a history of everything (well, a history of hits on my blog since my last meltdown in April), it looks like this:

The top four posts were about stuff other than stuff I use. So it’s controversy that people enjoy. Nobody can resist a nice messy train wreck. Good thing, I guess. Lots of train wrecks on this blog.

Other wildly popular posts were the Crisis in the Community post, and some of the unfortunate nonsense about the incredible difference between the words “banned” and “blocked”… which fortunately didn’t survive the meltdown.

So, what does this say about CAD? It seems the pursuit of entertainment trumps the pursuit of knowledge. Even on a work related blog. So from now on, it’s just ridiculous controversy.

The most unfortunate thing about those statistics is that if there were any posts I could go back and rewrite, some of those Synchronous Technology posts would certainly be some of them. The main thing was that I didn’t know anything about ST, and seemingly neither did anyone else who was writing about them. I wanted to get people to start talking about it, so I just said what I thought it was based on only the silly marketing stuff I’d heard, read and seen.

What I thought funniest was that people who didn’t know any more about it than I did were telling me I didn’t know what I was talking about. Well, of course I didn’t! and neither did they. No real info was available! Not knowing was the whole point of posting! To learn. There are a lot of differences between CAD people and CAD journalists. I’m clearly not any kind of journalist. CAD journalists want to look like they know everything even when they don’t. CAD users are really just in search of information and application.

What do I think ST is now? I think I’ve heard people say that you can either use the parametric side of Solid Edge or the Synchronous Tech side of Solid Edge. So they are two different softwares. FrankenCAD might have been off the mark. More of a Jeckyll and Hyde CAD.

I think it’s a direct modeler that uses feature recognition and applied dimensions that combine to work like parametrics applied to the finished geometry rather than parametrics applied to underlying sketch geometry.

100X faster? pppbbbtt. Than what? This sound very far fetched. I can see where no history is much faster than a big tree, but I can also see where feature recognition probably takes more time than anyone will admit.

SEwST sounds cool and useful, but very limited. This is where I branch off into conjecture… It is limited first in the types of edits it can make to limited types of geometry. First of all, it can not handle changes to general NURBS shapes, meaning spline type complexity. I haven’t been able to get anyone who has used the stuff to talk about it. They (SEwST promoters) probably don’t know either. Spaceclaim has limited capabilities in this area.

I’ve been tempted to recreate the SEwST Youtube videos in SolidWorks. Not because I think SW has exactly the same functionality, but just to show that you shouldn’t believe everything you see in a Youtube demo. I really think I could make SW do the same stuff, and make it look stupid easy.

Is this as revolutionary as parametrics was? No way. This is direct editing, which has been around for decades, topped with a combination of things that works like parametrics, heaped with an overly generous helping of hype.

Will it be useful? Yes. Direct modeling inside SolidWorks has already been useful to me for years.

Will it change the CAD industry? Most of the players in the parametric movement already have direct editing. There were several other direct modelers before SEwST. SEwST has built on the Spaceclaim model, and improved it somewhat – although I must clarify I’ve actually used Spaceclaim, but haven’t used SEwST.

Is the CAD sky falling? Not unless your initials are JB. You can’t see what’s going on behind the scenes, but outwardly, I’m not hearing any reaction from a CAD company either endorsing or condemning the direct editing movement. I do expect CAD companies to add more direct editing tools because these days CAD companies are as bad as cosmetics manufacturers with the amount of wheel spinning on useless trends (for example, the ribbon, Vista, realview type functions).

Wow, I went further down that trail than I hoped. SEwST has yet to deliver on a lot of outlandish promises and expectations. The rest of the CAD world is not yet trembling in fear.

Catia V6 – Synchronous Technology on Steroids without the hype

June 18th, 2008 1 comment

Ok, this’ll get tongues wagging. Now that I’ve learned a little, or think I’ve learned a little about Synchronous Technology, I learn that the only thing that’s really unprecedented about it is the amount of useless jaw movement it has caused.

Check out these Catia V6 youtube videos:

 

Huh. Well if that doesn’t look an awful lot like ST or SC, I don’t know what does. It seems to be called Catia Live Shape. I have exactly zero actual information about it other than what I can see in these videos, and the Martyn Day article I linked to in a previous post. The second video was posted in March, right before the Siemens media onslaught started. So who is it that is playing catch up? Neither product seems to be truly market ready yet, so it remains to be seen who delivers this first to paying customers.

But the geometry creation tools are only the tip of the V6 iceberg, and not even the tip that the Dassault marketing folks seem most interested in, either. Collaboration, PLM 2.0, Web techniques, virtual immersion, “experience” all seem to be more interesting to DS.

Here’s another one where Bernard Charles explains what PLM 2.0 is all about. I can’t really understand it, but that’s because Mr. Charles Franglish is further slurred by the low quality youtube audio. If anyone figures out what he’s saying, please leave a comment.

 

So, Catia seems to be more focussed on PLM 2.0, and really big picture stuff more than the small potatoes of making and changing geometry.

And finally, the above piece is I think the most powerful statement they make about V6. The virtual host, with her virtual hand and head gestures, right down to the virtual stretch of her blouse between her virtual breasts. This company believes in this virtual reality immersion in a way that wasn’t possible the first time the VR wave hit almost 10 years ago. The first wave led primarily to the proliferation of games. This wave may lead to the proliferation of industrial simulation.

Anyway, ST is not the only game in town. I think Siemens saw a window of opportunity, and it just happened that the window didn’t correspond to a time when they had a real product to sell. Siemens main hope was to strike first, even if it was just a virtual strike.

Even more synchronicity…

June 11th, 2008 6 comments

I have to admit, I was originally kind of interested in this Synchronous Technology topic, but I’m quickly getting over any sort of interest that I had in it. I’m catching a fair amount of crap for it, and not really getting what I think are very good answers. Since I can’t rely on finding anyone with an objective opinion out there, I’m just going to have to put this on the shelf and wait until maybe someone from Siemens sends me a copy to review (hint, hint).

Siemens has started selling this “pig in a poke” at a greatly reduced price (~$3000 - in a notice from a reseller who spammed some forums). The price seems to suggest that they see Spaceclaim as their main competition, even though they are asking you to “trade in” your SolidWorks license to do it. Of course they can’t actually take your SolidWorks license, so the whole thing is just a stunt.

Another thing that confuses me is you hear these marketing testimonials about how company X is seeing such great improvements, but at the same time you can’t get a straight answer out of anyone who has actually used it about functionality because the software is not going to be available until August.

The fact that no one can really descibe it succinctly in a way that makes sense says everything they need to say about it. So if I can’t get users to say anything intelligible about it, then it remains just another glossy ad with nothing behind it. The part that really irks me is that the people who say I’m just criticising because I’m devoted to SolidWorks are waving the SEwST flag without any personal experience whatsoever. I am at least looking for objectivity.

One of the fellows who posted a comment here sent me a couple of long emails which are equal parts rant, defense of MS Ribbon interface, incorrect memory, self contradictions, and underdog flag-waving. Scott Wertel it seems is a fan of Alibre and Solid Edge. He claims CAD is just a tool, but also defends zealotry. I’m not sure what to make of this contradiction. He claimed I had changed my mind about the SW 08 interface, but later recanted, because he was obviously wrong about that.

Anyway, this is really long, but it explains a few things. I’m trusting that Scott’s one view of this stuff was enough to give him the correct impression. Here is what Scott had to say, with comments interspersed:

===============================
Religious zeal

One of the things you have to realize is that the SE community and SW community are made up of entirely different types of people.  The SW community is very passionate about SW.  I (k)new a guy who went unemployed for 6 months because he wouldn’t take a job working on any other software.  That’s asinine.  CAD is just a tool.  The SE community, as a whole, agrees with that philosophy.  CAD is only a tool.  If it works, great; if it doesn’t, find another one.  So far, SE works.  When it doesn’t, I make a call report direct to Seimens and get an answer.  The times I worked for companies that utilized Works, I was greatly dismayed by the type of support, or lack of support, that VARs provide.  Perhaps that explains the difference in passion for a software.  Or perhaps it is because SE users know that SE works (as well as any other mid-range MCAD software) but not many others in the world have even heard of it.  It is always a struggle explaining to people that we use SolidEdge, not SolidWorks.  Honestly, people always try to correct me “…you mean Works?”  “NO!  I don’t.”  But I digress.
 
I will tell you, though, that this religious zeal you speak of is a community response due to the fact that SE finally has something new and unique to differentiate it from the competition.  More importantly, Seimens is actually marketing.  SE has never, read that NEVER, been marketed effectively and the community is ecstatic to have something to grab on to.  So there is a difference between religious zeal of Synch Tech and the fact that users are just excited about having something worth showing off, before the competition has it.
Skeptical
Being skeptical is good.  I think you are getting a lot of chatter about this because of the stance you have taken.  Basically, your speculation is so far off base that people feel the need to correct it, and then the discussion tends to get a little heated.  Oh well, it happens.
 
I will concur that I am very skeptical.  My blog post about ST was written because the little sneak peak I had helped with some of the skepticism, but still shows that A LOT of training is going to be required for this roll-out.  The bullet points were written specifically for the SE community.  Many of the vocal users of the SE (via newsgroup) have issues with the insane ease-of-use for any idiot to make a change.  How do I protect the design and intent that goes into a specific part is the big question?  The bullet points answered that question to those who know enough about ST.  So although the blog didn’t say a lot, it really did.  I’ll be happy in future correspondence to illustrate why.
===============================
 
When you have only the info that marketing feeds you, which is probably intentionally incomplete, and almost certainly exaggerated in some way, people speculate, looking for the truth behind the hype. Speculation is a guess. Guesses can be wrong. I keep guessing about stuff and asking for verification from someone who has seen it because I want to understand. I do think that this technology does have the capacity to be useful, but really its just another tool. Because it is not going to do away with history based approaches, it cannot be as revolutionary as the original history based revolution. To deny it has any importance would be wrong, I think, but some people are certainly overstating the case.
Also, if this is going to take a lot of training, doesn’t that contradict the whole “ease of use” mantra in the first place? This is why I don’t think Siemens really has a great message for the technical user. It doesn’t fit the low end user, and doesn’t eliminate the specialist knowledge needed to run history based CAD. This is part of the reason I don’t get it, and why I think it is not going to be the block buster people are assuming it will be.
 
============================
180ed
I could have sworn you wrote an article on how the SW08 UI was actually very efficient once the user got used to it.  My apologies if I mis-spoke.  But, can you blame SW or SE for going this route with the UI?  More people are familiar with Office 2007 than they are any CAD package.  Getting to know one means you’ll get more comfortable with others.  Not to mention, do you pay a small licensing fee for the Vista-like UI, or spend a small fortune developing your own?  I think we’ll see many more Windows-based programs with a similar UI.  I’ll say that it makes no difference to me.  I’ll adjust and be just as proficient.  I managed to do it in Word and Excel, I can do it with CAD, too.  Just need an open mind and willingness to climb the relearning curve.
 
The one thing really interesting about the new UI is that it has so much in common with SW 08 UI, that there is no differentiation between the 2 packages if it wasn’t for Synch Tech.  The same parasolid kernel running the same UI to make the same end-items.  The only thing to choose when picking a CAD package would be cost and support.
===============================
 
Apology accepted. UI? Hold it, what are we talking about here? Ribbon UI is widely reviled. Some people like snakes or spiders as pets. Sure, you can find people out there who like the Ribbon. SW doesn’t license the Ribbon, they did spend the money to develop their own, as I heard the story. Interestingly, I think SW changed their interface at least in part to differentiate themselves from “the rest”, but it has backfired, you’re right about that, everybody looks the same more than ever now.
 
================================
CPDA White Paper
Interestingly enough, I haven’t seen that white paper yet.  I’ve seen just about every other one, but not that one.  I did a quick glance through it and want to point you to the last figure.  In it, D-Cubed and Parasolid are on the last rung, Synch Tech connects the two and is a bridge to the main CAD package, either SE or NX.  The point to make here is that this layer is a completely new technology.  Whereas D-Cubed and Parasolid are open technologies, meaning Seimens will license it to anybody, ST is as proprietary as one can get.  It will never be licensed, sold, or shared.  As far as facts go, that is about as specific and we can get because all the employees at Seimens have been incredibly hush-hush about it.  I don’t know if you are aware, but Synch Tech is one of the reasons Seimens bought UGS.  ST was in the development stage during the acquisition and was one of the major selling points to the future value of NX and SE.
 
Solving relations
This is where the confusion lies and where speculation has ruined the experience, as does the “Synchronous” title.  Synchronous does not necessarily mean at the same time.  Most importantly it doesn’t solve assembly relationships and sketch relationships at the same time.  There are no sketches.  There is not even a sketch environment.  There are some 2D geometry creation tools, but that is to only aid in defining regions on a surface or plane to create 3D geometry.  Once the 3D feature is created, the 2D geometry is absorbed – it no longer exits.  The dimensions placed on the 2D elements have been transferred to the 3D geometry.
 
I’ll try to explain with an example.  Start by “sketching” a square and extruding it to create a box.  Once you create the box, the sketch is gone.  The horizontal and vertical dimensions used on the sketch now define the edges and/or side faces of the box.  The sketch is no longer needed.  If I need to change the size of the box, I can find the feature in the feature list because it does exist as a feature, and then edit its properties.  Or, I can just add another 3D dimensions (like PMI dimensions) and change its size.  Once I finish the command, the dimension is absorbed into the feature.  It’s there, but not there.  I can either find it again, or just create another dimension if I have to make a subsequent change.  There is some logic behind removing duplicate dimensions, but I don’t have any specifics on that.
 
Now add a cylindrical boss to the box.  Like before, you kind of start with a sketch but not really a sketch.  If you had 3D wire frame geometry, or intersecting edges, or any other geometry you could use it to create a circular region (projected if need be) onto the surface of the box.  Go ahead and dimension the circle to get the right size.  Once you extrude it, the region and dimensions get absorbed into the 3D feature.  Click the edge and change the circular edge’s diameter.  Or, apply a new dimension to the circular edge to change its diameters.  Click on the cylindrical surface and a dimension diameter appears there, too (if I remember correctly).  Delete the initial box, and the cylinder remains because it is not history dependent on that base feature.  Keeping the first box there, add another boss on the open size of the cylinder so the circular edge disappears, you can still change its diameter without having to roll back the new solid feature to “find” that edge again.
 
This is not direct editing, or explicit modeling, or using push/pull/move face commands that add yet another feature to the history tree.  (Yeah, everybody has got those.)  This is on-the-fly changing the parameters of the solid without having to worry about how it was created.  This is because of how Live Rules determines relationships, not D-Cubed or Parasolid.  Live Rules is that ST layer between D-Cubed and the CAD application.  Your basis that building ST on the foundation of D-Cubed is on shaky ground is correct, if it actually were based on D-Cubed, which it is not.
===================
 
When I talked about solving sketch relations simultaneously, I was talking about SW with D-Cubed.
 
“Synchronous Technology” I will take to be a marketing buzzword, with as much meaning as “Sausage Integrator”.
To be fair, in the image you cite (captured from the white paper below) looks asmuch like D-Cubed is part of the foundation of ST as anything. ST is on top of D-Cubed just like a house on a foundation. I think you’re trying to pick and choose your analogies to make it look better than it is. The fact that D-Cubed is what ST is built on top of is at least cause for concern. 
 
 
=============================
Live Rules
I brought it up, I might as well try to explain it technically with some examples.  Dan did so, and based on your blog I think you understand, but let me elaborate.  FYI: It is something to be excited about.
 
Take for instance you want to create sweep.  The commands in SE and SW are the same. Create a sweep path (usually 2D sketch but can now be a 3D sketch) and a 2D cross section of the profile to sweep along the path.  In the path sketch, you need to apply fillets to all the corners, the fillets need to be of a the proper radius to make sure the solid doesn’t buckle when wrapped, and most importantly, you need to make sure that you have tangent relationships created between the lines and arcs (via D-Cubed).  What happens if you accidentally delete the tangent relationship?  The line and arc and still tangent, you didn’t alter the geometry, but SW or SE (i.e. Parasolid) is too stupid to know that they are tangent.  With live rules, it finds tangency based on actual physical geometry and not applied constraints.  It does it on-the-fly, it does it live.  In this case, synchronous may be that it finds not only the geometric constraints, but also geometry constraints (hard to differentiate).
 
Now take that example and apply it to solid geometry, not sketches.  I have a box with the edges filleted.  I don’t have a tangent relationship between the fillet and the sides.  I have geometry that is tangent, physically, so live rules picks up on this and uses it.  If I want to lock-it-in, so to speak, or always make something tangent (or coplanar, or parallel, or whatever), then you can add what are called “persistent” live rules between the geometry.  This is more liken to assembly relationships, but on the 2D part.  To do this in old SE or SW, you would have to create that geometry in the sketch just the right way to be able to apply that D-Cubed relationship.  What if you can’t sketch a 2D cross section like that?  No worries with SEST, because they don’t even have to be the same feature to have relationships exist between them.  They don’t even have to be the same part in the case of ST for assemblies.  This is a fundamental change in solid model methodology.  It truly is amazing (and different) but the only way to grasp it is to experience it yourself and that won’t happen until August.
 
The other example I like about Live Rules is the fact that there are no parent-child relationships.  What was a child, can become a parent.  Have you ever wanted to keep a hole centered, and then the face of the solid a certain distance from the whole?  You can plan that out with layout sketches and other “guru” methods, but you always have to have that surface first and the whole dimensioned to it because you need solid geometry to cut the hole from.  If I want to keep the hole in the same place and move the surface, I would have to really dig into the feature tree and find the design intent to make sure I lock down the right dimensions and change the other ones.  Usually it requires changing the size of the block, then going into the hole feature and changing its locating dimension by the appropriate amount to move it back.  With ST, you just add a dimension between the hole and the surface, change the dimension (clicking the button to lock the hole’s position for this edit) and the surface will move.  Very easy.
 
Do you have design intent where you need to keep certain things symmetric?  Not a problem, because you can lock symmetry so a single dimension change to one surface will actually move the opposite side surface by the same amount to maintain symmetry.  Again, live rules.  But that is where a lot of rank and file SE  users are scared of Live Rules.  How much does it pick up?  How does it find what it associates and changes automatically?  How can I force it to only change what I want, locking in other geometry if necessary?  Live Rules makes it very easy to make change, almost too easy.  How can I be assured that some purchasing agent, or machinist isn’t accidentally altering geometry he shouldn’t (besides using PLM or file security measures) while they are viewing the file?  And that is also where the big learning curve is going to come in.  How to become proficient at what associations live rules makes on the fly and what it doesn’t, and when I need to add explicit relationships and when I just need to hot-key an override.
 
Right now, rank and file SE users know as much about SE with ST as you do.  We are scared, but welcoming the change with a bit of pessimism.  It is new, it is revolutionary, it not just hype.  But we won’t know the total implications of this until it released in August and we actually get to use it.
===========================
If a 3D path is something new for a sweep in SE, no, SE and SW are not basically the same. None of the requirements that you cite are requirements in SW, except under special circumstances.
You’re talking about feature recognition, which is another very iffy sort of thing. The rest of this sounds reasonable.
===========================
History
Yes, history can still exist.  For the first few releases, if not permanently, users have the option through an administration control panel to turn on ST or not.  If the admin turns it on for the users, they still have the option of modeling the old way -with history – or the ST way.
 
Speculation
I don’t think any seats of any CAD package are going to be converted to SE just because of ST.  I do think that a lot of SW or Inventor houses will buy one seat of SE with ST just to be able to handle imported geometry easier.  I think customers debating between SpaceClaim, CoCreate, or KeyCreator will now look at SE with ST instead, because it appears to be the best of both worlds, plus a drafting package to boot.  Will they buy?  Who knows.  I don’t think this answers all of our prayers.  I do see a lot of machine shops picking it up for that reason.  A lot of CAM packages handle imported geometry well, but this is a way to clean up some of it before going to CAM, if necessary.
 
I think SE with ST is a great buzzword.  But beyond that, I think we are looking at a revolution in CAD the same way Pro/E revolutionized CAD in the 80s.
===============================
My thing with history is “can you do both in the same model?” Is it one or the other, or can you do both? The meaningless “synchronous” implies both.
I have strong doubts about equating ST to the Pro/E revolution. With Pro, it took a long time for other companies to challenge their dominance. That wouldn’t happen today I think because of the vicious competitiveness of the market.

What I think I’ve learned about Synchronous Technology

June 7th, 2008 14 comments

I’ve been guessing a lot about what functionality the term Synchronous Technology was meant to obfuscate. I’ve been both wrong and right about some of my guesses. I’m not the only one. Even Evan Almighty has been wrong and right, but mainly irrelevant. Very few people have any real “facts” about this stuff. We hear what some people want to be true, and some people just blindly repost press releases without any idea at all what it means. We’ve heard some strange emotional rants about why the world needs something like this as opposed to something or anything else, and some equally strange posts seemingly defending SolidWorks from the need to keep up with the Joneses.

I’ve been lucky enough to have Dan Staples of the Solid Edge development team and Chris Kelley, a Siemens marketing guy both stop by the blog here and leave some comments. Dan in particular has been very helpful with the only hard facts I’ve heard anywhere about Synchronous Technology. Even the ST white paper is very heavy in vague declaratives. The truth is that most of those videos posted about ST, well, I’ve been tempted to post equivalent videos of SolidWorks doing exactly the same thing. Not because I have an axe to grind, but just to show that the examples we have seen of ST have been unconvincing because the capabilities already exist in SW and other places. This is why some folks have said ST is nothing new. I think Siemens has done a wonderful job of creating hype, and a less than wonderful job of backing it up. But of course that may be the main attraction of hype – not backing it up is what makes it hype in the first place.

So what have we learned?

- Synchronous Technology means that all of the relations in a part are solved simultaneously instead of linearly.

In SolidWorks, mates in an assembly are all solved simultaneously. So are sketch relations. These are driven by D-Cubed, also owned by Siemens. What are two of the least reliable areas of the SolidWorks software? You got it, sketch relations and mates. Go back and count how many times I’ve singled those two areas out as things I would like to have fixed. I think this is a bad omen for ST. D-Cubed proves that simultaneous solutions are not an incredibly reliable source. Of course SW’s problems could be an implementation issue, and it still remains to be seen how Solid Edge’s implementation of simultaneous solutions for relations within a solid model is going to work in real every day modeling.

There is no doubt, history can be a cumbersome way to create geometry, but it is also just as often a great asset when making changes. Getting away from history is a great theory, but based on what I’ve seen of simultaneous solutions, there may be a reason why other CAD companies are not flocking to it.

- Synchronous Technology really is something new – a new way of putting together a lot of old stuff.

“Synchronous” can mean “solving relations simultaneously”. Or it can mean integrating several modeling technologies or techniques. I think the “synchronous technology” term benefits from some intentional double entendre, but at the same time is sufficiently vague that it doesn’t mean anything in specific as a stand alone phrase. All of this probably makes sloganeering marketing people wet their pants in glee. Still, clever new names or not, this is all familiar territory.

Simultaneous solutions? Check. D-Cubed. Shaky foundation. Been there, done that.

Driving dimensions and geometrical relationships on “dumb” geometry? Check. Spaceclaim.

Feature recognition? Another shaky foundation. Check. Several CAM products use this, as well as FeatureWorks.

Live Rules? Behind the marketing name, this is indistinguishable from parametric relations. In fact, it looks much like parametric relations applied directly on the solid model. Dan sort of confirmed this, I think. Parametric relations on a solid model to me is the one thing to really get excited about with ST. The screen grab below was taken from a youtube video.

- Siemens is totally changing directions in the high end and midrange markets, and is throwing this Hail Mary in the hopes that all the commotion may attract more attention than all of the Spaceclaim and CoCreate non-news.

With Synchronous Technology, Solid Edge has removed itself from the SolidWorks – Inventor fray. They have been removed for some time, they just never admitted it until now. Personally, I think the hype has been brilliant, but the failure to follow up the hype with some sort of intelligible scheme that real users can understand leaves the whole thing looking like the vacuum cleaner salesman saying “trust me!!” It’s kind of telling that I had to dig this info out of people, and that Siemens clearly does not have a clear and intelligible message for users.

Chris Kelley appears to be a one-man Solid Edge blog machine, but he is marketing, not technical. Really, are there any technical Solid Edge blogs out there? Why are they not giving us the low-down from a users point of view (or are they and I’m just not seeing it?) I’m not bashing Solid Edge as a product, I don’t know enough about it to bash it. It seems so much like SolidWorks as to be practically the same, historically, anyway. But the product hasn’t seen the broad industry acceptance that SolidWorks has seen, so Siemens had nothing to lose by changing the rules and aiming low.

What I mean by “aiming low” is that the whole direct editing movement seems to be enthralled with the ease of use idea. I think this is meant to expand the definition of a “CAD user” to mean someone lower on the specialization totem. The message here is “ease of use” rather than “power” or “control”. These ideas always seem to be diametrically opposed.

- What remains in Solid Edge is no longer a history based modeler.

Some people who don’t know (including me) have said that ST is Spaceclaim bolted on to SolidWorks. I don’t believe this to be the case. I’m now under the impression that ST is Spaceclaim bolted on to CoCreate, or there abouts. There is no history left. Siemens has abandoned history based modelers. This seems to be one of the things that Dan was saying.

Many UG users I have known have said that UG never was much for history based modeling, and with Solid Edge showing as an “also ran” in the parametric history based market space, it is no surprise that they decided to changed direction, possibly if for no other reason than to distinguish themselves from SW and IV. So now they have a chance of being on the top of the heap of non-history based modelers, and trying to capitalize on the wave of direct editing modelers really rejuvenated by the popularity and simplicity of Sketchup, and given a shot in the arm by Spaceclaim.

Summary

Solid Edge and Unigraphics/NX are both strong products, but they aren’t market leaders. Solid Edge was acquired from Intergraph, and part of NX is SDRC. How is Siemens going to grow this set of products? A bold move like completely rearchitecting the software might not have been inevitable, but it really isn’t a huge surprise.

I’m very interested to see what rank and file Solid Edge users think of these changes. For those that are happy with the history-based view of the world, Solid Edge may have just handed SolidWorks a small infusion of new customers. There are several people who are not paid by Siemens who are going around claiming that this stuff is the answer to all their prayers, even though they have never laid hands on the software or fully understand how it really works.

I’m going to guess that the new Solid Edge will have a little burst of sales just due to curiosity, but in the end, interest will wane. There is a reason why products like IronCAD, CoCreate, KeyCreator and Spaceclaim have not become overwhelmingly poplular while products like Pro/ENGINEER, SolidWorks and Inventor have. I don’t think a massive hype campaign is going to be enough to change this decades old momentum.

It may be a great idea, and it may have required some revolutionary thinking to bring it to fruition, but I think Synchronous Technology is going to become another forgettable buzzword that marked a sharp turn in the road for an “also ran” history based modeler.

The CAD industry is split by history

May 23rd, 2008 13 comments

I understand confusion when I see it. Different segments of the CAD industry are moving in different directions, and it is by no means a given which direction is the correct one. In the end, I believe we are going to see more direct editing (non-history) based tools, but I don’t think FrankenCAD is the obvious choice.

In one corner we have the noisy, but still rather stuffy Siemens/UGS with its Synchronous Technology pom-poms and cheerleaders, claiming that history based modelers are going to give way to non-history based direct modeling, or at least mixed modelers which employ non-history based modeling within a history-based framework. This is an ugly FrankenCAD mix, and as details leak out, I don’t think it gets any prettier.

And then in the other corner we are seeing the budding romance of a non-history based modeler (Spaceclaim) with another non-history based modeler (Rhino), but then one of them goes and adds some history based functionality. Rhino with implicit and explicit history shows that the direct editing crowd understands parametrics has value that they can’t deliver. This is FrankenCAD from the other direction. How does adding random parametric history dependent features to a non-history based model work? This sounds rather like CoCreate software, which is another also-ran in the direct editing miasma. This story of Spaceclaim and Rhino teaming up and Rhino adding history isn’t getting as much press as the other Synchronous story, but I think it is the more important of the two.

Here’s why. Oreos. Yes, oreo cookies.

Spaceclaim on its own is limited. It has cool editing capabilities, but they are limited to analytical geometry – prismatic stuff with lines and arcs, single curvature, developable surfaces. It has some limited capability with general case NURBS shapes, but it is really limited. You can make simple machined parts and sheet metal parts, but more complex castings and plastic parts aren’t really part of the Spaceclaim equation. What Spaceclaim is missing is exactly what Rhino is best at – swoops. And frankly, Rhino, in all of its complex shape surfacing glory, is no match for a solid modeler when it comes to prismatic work. Plastic part engineering in Rhino would be tedious. What Rhino is most missing in its software is exactly what Spaceclaim does. Oh, and they are both direct modelers.

Everybody has been waiting for Dassault or Autodesk or PTC or UGS to swoop down and snag Spaceclaim, but it keeps not happening. What is happening is that these two small, rogue, direct editing CAD companies are starting to work together. It’s like an Oreo cookie. The wafer is good, but I wouldn’t eat it by itself. The filling is also yummy, but by itself isn’t satisfying. Put them together and you’ve got something that stands the test of time. I would like to see these two companies do more than just share files.

We’ve heard a lot of explanations about what is going on with Synchronous Technology, but the message is getting more rather than less confusing. At first it was just direct editing tacked on to parametrics, Spaceclaim bolted onto SolidWorks. Then it became something far more than that that mere mortals could not possibly understand, and self-proclaimed brilliant people could not explain. Now it appears to have many aspects to it, including everything previously mentioned, procedural features, form features, and feature recognition. That’s an awful lot of “features” for a direct editing (non-feature-based) modeling scheme.

Secretly, I’m hoping that it might be condensed to a statement something like “parametric relationships brought down to the final model faces, rather than intermediate features”. So you make geometry somehow, anyhow, and then put parametric relationships directly to the faces. You get the benefits of paremetrics without the overhead of history. This is something I wondered about in an earlier post. I’ve been writing a lot about the direct editing conundrum for about a year, mainly due to the appearance of Spaceclaim on the scene.

The alternative to a simple statement of the software seems to be something that is too complex to trust or use. Siemens is using the term “feature recognition”. Feature recognition is something I’m familiar with from two sources – FeatureWorks, which is one of those 40% solutions, and FeatureCAM, which also recognizes features for machining. In both cases, a lot of manual intervention is required to do real work, and in both cases, it works best on very simple geometry.

Another warning flag on the Synchronous stuff is that when I have mixed modes in SolidWorks (history based parts with direct editing features), you get a lot of confusion about how to change things at the end of the tree. Geometry gets “double jeopardy” because you could change it using either history based or direct editing features. Especially if multiple people do the work, this will add to the confusion. The mixed modeling that Synchronous Technology represents is an ugly frankenCAD, in my opinion. Cool idea, yes, but I think in practice this is going to be a bad idea. People will prefer a clean break.

In all of the times I have heard top SolidWorks users talk about the direct editing tools in SolidWorks, they have done it from the point of view that these tools are cool, and can make some tasks easier or simply possible, but they are also a best practice nightmare in terms of maintaining editability, and that its a sloppy way to work.

To me this suggests that if you’re going to move from history to non-history, it is best done either sparingly within a single CAD file or by moving from one CAD file to another, even moving to a different application. Once you start doing direct modeling on a part, switching back and forth causes a lot of confusion.

History based modeling is not going to disappear, let’s be clear about that. There are too many proven benefits. I’m sorry if sometimes history based modeling is intellectually difficult. I’m sorry about that. How else are you going to get the history based benefits of things like the shell feature, or fillets? History is not history.

What’s happening here is that the CAD industry is again appealing to the CAD bottom feeders, a trend that seems to be gaining momentum in an effort to expand the CAD market into new areas it hasn’t previously occupied. People who can’t hang with the intellectual/training demands of history based modeling are going to go for direct modeling. But I don’t think it’s a given that they are going to flock to the unnatural FrankenCAD combination of history and non-history modeling.

It boils down to this: Machinists and people doing simple concepting work will use direct editing because its a no-brainer (think Sketchup) and less expensive. Engineers responsible for production models will still use history based modeling because it represents more complete control. To the extent that you have both types of people in the same organization, it may make sense for that organization to get one tool that does both, but honestly, direct editing comes at the end and the beginning of the project. At the beginning, their models are used as reference, but the production model is made from scratch. At the end of the project, it doesn’t matter because edits are for mfg, for example adding stock, and won’t be pushed back up to the engineering model.

As an aside, all the references to Synchronous Technology so far have been with respect to solid modeling, not necessarily to surface modeling. Add to that the seeming lack of capabilities around complex shapes, and I for one will not be able to make use of this concept at all. I will be much more likely to be able to use whatever comes of the marriage of Spaceclaim and Rhino.

Spaceclaim + Rhino = solids, surfaces, prismatics and general NURBS, mainly direct editing with some history

Synchronous Technology = solids, prismatics, mainly history with some feature recognition and a lot of unknown details

To me, the Spaceclaim/Rhino FrankenCAD – SpaceRhino – seems like the more attractive combination. A big part of the reason for that is that you can see what that combination is, and what it does. This Siemens thing is still too much of a pig in a poke.