Tuesday, 17 June 2008

Synchronous Technology from Siemens - History-Free modelling - Myth or Reality?

Of late the CAD Market has been active with discussions on the 'new' technology marketed by Siemens as Synchronous Technology - a new paradigm in Mechanical CAD. Some CAD gurus term it revolutionary, path-breaking and a panacea for the ills of Parametric Technology ( not PTC !), while other seasoned users and I-have-seen-this-often CAD specialists want to be cautious and adopt a wait-and-watch approach.

One of the common thread underlying the discussions on Pro's and Con's has been that Parametric approach has been beset with two issues , namely errors during regeneration and time taken to edit a design having a long history-tree. Hence history-free modelling approach seems to offer a solution to these issues. Instead of taking extreme stand with respect to either History-based or History-free approach, a middle path trying to capitalize on the benefits of both approaches seems to be emerging. This is definitely a positive trend for the 3D CAD Industry and the user as well.

From the perspective of a Design Engineer using 3D CAD, following points remain in focus for any tool to retain its popularity and acceptance:

1. Ease of Use
2. Bi-directional Parametricity with easy-to-generate-drawings having driving dimensions
3. Tolerance Analysis for stack-up calculations
4. Knowledge Management for re-use of design procedures
5. Design Drawing Automation
6. Error-free 2D Drawing for downstream usage in Manufacturing, Inspection, Assembly, Service among other functions.
7. Dimensional Management for Fit, Form and Function

Most of these requirements would need parametricity, constraints, relations between Features of Sizes that goes well with Parametric History-based approach.

One of the points that needs to be addressed critically, is Freedom to Edit Designs developed on any CAD system. Let us look at a scenario wherein an organization develops a design and transfers the same to another manfuacturing facility for prototype development. If the Design data can be changed inadvertantly without leaving a trace of the change (read history-free) it sounds scary with obviously undesirable implications! Freedom can result in abuse !!

Every technology has its advantages and dis-advantages.

Development of 2D Drawings that enables parametric updates and changes to dimensions need to have higher focus. This gets complicated with History-free approach on account of the bi-directional facility enjoyed by the Engineering community.

Simply said, History-based technology provides a facility to Undo, Modify and Redo a design concept at any stage in design process. History-free approach necessitates correctional approach that may involve re-work. Things done in a fraction of a second may require more steps with History-free approach. Parametric dimensions on a drawing would necessarily have to be re-visited by the Designer when a model undergoes a change in History-free approach while it would not be so with History-based approach.

I guess a consensus would emerge with more players such as SolidWorks (that already has Instant3D and SWIFT to address direct editing and regeneration/re-ordering issues) working on ways to address this requirement without sacrificing on the benefits currently enjoyed by the Design community.

Convergence of methods is sure to be in focus for time to come. At the end of the day, Users would be the winners !!


  1. Ya. I agree with you. Parametric modeling looks safer. One of the simple example: I can suppress and unsppress a feature depending on design variations or during design iterations. But how it is possible in direct modeling?

    We have appreciate the new technology. But in reality how it can help a designer to do his job better?

    It is still a question mark for me. Let us wait and see .....


  2. This is not really a convergence, this is one approach or the other. You can use the direct editing technology or the parametric technology. But you can't use them both at the same time on the same data.

    It's realy like having two separate software packages, which is the part that Siemens is not communicating very well.

    You are also completely stuck if you have any geometry other than dead simple prismatic shapes with round fillets. No options whatsoever with general NURBS shapes.

    I think for very simple parts, this will be useful, but only marginally more useful than any of the existing tools that do the same thing or nearly the same thing. The only really unparalleled thing here is the hype.

  3. Dears, i have been a user of both works and Edge for the last 7 years. In my opinion there was no difference between the two except a few bells here and a few whistles there. While Solid Works would always keep point no.1 "The bi directional associativity between model and 2d views" as a must have, i am yet to see anyone using that in real production environment.
    Same goes true for many a things at Solid Edge level.
    However, synchronous technology from Siemens surely seems to be a diffrentiator, let's give it to Siemens for their real breakthrough. I am sure if Solid Works would have come out of this first, they would have blown even bigger bells and Drums.
    I also saw the video from Solid Works ridculing Synchronous Technology by making a few changes to a engine casing, the video showed Works took 13 seconds with Traditional modelling approach to change the size of the hole, while the same change with ST took a second.
    So once again guys, let's give it to Siemens PLM and let the user be the real judge.
    Any technology that get's launched has room for development. This is the first release and i can see it is production ready for prismatic components atleast.

  4. I keep hearing "parametrics" and "history" being interchanged as if it is the same thing. It is not! Solid Edge with Synchronous Technology still has parametrics in the ST model, what they do not have is the multiple layers of associative dependency (history). This means I can still drive features with dimensions and I can have one parameter drive another without having to worry about a face being deleted, which orphans a sketch plane, which orphans a sketch, which fails a feature.