Just so the effort isn't lost on the general market, Dassault has renamed this latest release V5 to V5-6R2012, a move officials say emphasizes its efforts around continuing compatibility and synchronization between the platforms. The interoperability bridge Dassault is building allows customers to transition to V6 at their own pace, still enabling those that do to collaborate seamlessly with departments, customers, and suppliers remaining on the V5 platform. V6 models opened in V5 will retain features created in V6 -- for example, models that leverage V6's Part Design, Sketcher, and Generative Surface Design workbenches and knowledgeware can be viewed as such in the older version.
Besides helping to avoid the crushing customer fallout from moves past, this extended emphasis on V5-V6 interoperability is really a good way for Dassault to encourage adoption of V6, allowing customers to make the move when they're good and ready. Here's a run down of some of the specific features making it into this release that advances its V5-to-V6 interoperability story:
Dassault has long claimed that compatibility between V5 and V6 is equivalent to the compatibility between the two releases of CATIA V5 and it continues to make that claim with this release.
Dassault R&D has inserted select V6 technologies in V5 solutions, including Class A surfacing innovations and concept design from CATIA Imagine & Shape.
Customers can reuse existing V5 models and other data in V6 hybrid product structures. As a result of this focus on openness and coexistence, engineers can create a single hybrid product structure that encompasses models from CATIA V6, CATIA V5, CATIA V4, SolidWorks, and even, officials said, Siemens PLM Software's NX and PTC's ProEngineer. As a result, design teams can conduct real-time design reviews and analysis of the virtual product regardless of what native authoring CAD tool was involved.
This is quite a feat for a software vendor. Usually there is some ability for a new version to use files from an old version. Being able to continue using the old version (updated) with new files is an advancement. It definitely shows sophistication in design of the software and data structures. It is often not effective to upgrade product versions in the middle of a design project.
I agree. I think Dassault and other CAD vendors have learned this the hard way from customer complaints over the years. This has historically been a big bone of contention, particularly among customers like A&D providers who have very protected development cycles.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.