2011 COE ANNUAL PLM CONFERENCE & TECHNIFAIR
CATIA/ENOVIA: WILL THERE BE PRICE INCENTIVES TO ADOPT V6 CONSIDERING WE WILL ALSO BE REQUIRED TO ADOPT A NEW OR ADDITIONAL PDM SYSTEM? THE COST OF A PLM IMPLEMENTATION WILL MAKE THIS A TOUGHER SELL IN THE CURRENT (OR ANY) ECONOMIC CONDITIONS.
CATIA V6 and V6 in general was designed and built to specifically address the needs and requirements of our customers for a system that can manage the complexity of current and future product designs, across geographically dispersed teams while maintaining the integrity of the data. To address these needs, CATIA V6 requires a database and the collaborative platform of ENOVIA V6. This should be confused as another PDM. While the depth and breathe of the ENOVIA Enterprise portfolio is significant, these additional capabilities totally optional and do not impact the cost of CATIA V6
CATIA: WHEN IS THE “END OF LIFE" FOR CATIA VERSION 5?
There is no end of life plan for CATIA V5.
There is currently no end date for customer support on CATIA V5. DS is NOT considering discontinuing V5 anytime soon. We have a massive ecosystem of partners and customers based on V5 and you won’t all jump to V6 immediately. Our customers need DS to continue development of V5, and that’s what we’re doing. We will continue supporting customers in production for/from the V5 platform.
CATIA: WHEN WILL THE V6 PRODUCTS HAVE (AT LEAST) 100% OF THE FUNCTIONALITY OF V5?
For the CATIA core technologies, Version 6 already covers 100% of the V5 functionalities. While the functional coverage for Automotive and Aerospace business processes is 95%, the coverage for Shipbuilding and Energy processes will be enhanced in V6R2013.
ENOVIA: WHO IS THE LARGEST CUSTOMER USING ENOVIA V6R2010 OR R2011 IN A COLLABORATIVE ENVIRONMENT WITH MULTIPLE COMPANIES?
(WHAT CUSTOMERS ARE IN PRODUCTION WITH V6R2010 OR GREATER WITH MORE THAN ONE COMPANY ACCESSING/COLLABORATING IN THE SAME INFRASTRUCTURE?)
Among DS Largest customers, GE is running a global collaborative platform with over 20000 users enabled on R2010 release. EATON is also among the largest with over 12000 users running R2010 release.
CATIA: WHAT IS BEING DONE ABOUT CONVERSION OF DATA FROM CATIA V5 TO V6 (AND BACK)? WILL V5 DATA WORK WITHOUT CONVERSION IN V6?
Version 6 is able to read V5 and V4 data. CATIA Version 6 is built upon the same geometric modeler as CATIA V5 and the V5 transition process maps all CATProducts and other V5 data elements into the Version 6 data structure.
The upward compatibility from V5 to Version 6 data is equivalent to the compatibility between two releases of V5.
Similarly, the downward compatibility between Version 6 and V5 matches the compatibility between two versions of V5.
Whether a company feels the value in migrating the models into Version 6 depends on its work processes and how its product lifecycle management solutions have been implemented. Version 6 supports hybrid scenarios and will support design in context, digital mockup, and other capabilities in mixed V4/V5 and Version 6 environments.
CATIA: DOES DASSAULT SYSTEMES HAVE A PLAN FOR MANAGING AND ACCESSING (V2), V3, V4, AND V5 DATA AS WE START TO TRANSITION TO V6?
HOW ARE WE GOING TO BE ASSURED THAT THE GEOMETRY IS NOT CHANGING AS WE OPEN OLDER VERSIONS IN V6? WE HAVE PRODUCTS IN THE FIELD BASED UPON DESIGNS IN THESE OLDER VERSIONS THAT CANNOT CHANGE ‘AUTOMATICALLY’, JUST BECAUSE WE OPEN THE MODELS IN A NEW RELEASE.
All V4 native formats to be visualized and printed are supported in V5 without any migration. Similarly, V4 and V5 native data can be viewed and printed without any translation in Version 6.
Regarding V3, only drawings can be viewed in V5 and Version 6 without any translation.
For upward transition, it is requested to use the standard Versions’ transition upgrade path.
CATIA: WITH THE MIGRATION FROM V4 TO V5 A LOT OF AUTOMATION TASKS HAD TO BE MANUALLY REWRITTEN DUE TO THE MOVE FROM IUA/GII/FORTRAN/UNIX.
WITH THE MIGRATION TO V6 AWAY FROM FILE SYSTEMS, WHAT GUARANTEES ARE THERE THAT OUR INVESTMENT IN APPLICATIONS AND AUTOMATION WILL CONTINUE TO WORK WHEN AND IF WE MIGRATE TO CATIA V6?
CATIA: WILL LEGACY APPLICATIONS BUILT TO INTEGRATE WITH THE CATIA V5 API CONTINUE TO WORK WITH CATIA V6?
These two questions are very similar and can be answered jointly.
C++ APIs as well as automation APIs have undergone changes between V5 and Version 6. There will be a Version 6 adoption effort that can range from very easy (part-level only macro for instance) to more complex (electrical, product-related for instance). Yet, the language, technology, and tools remain the same and early adopters can adopt V6 with limited effort.
Most complex changes reflect the integration with the collaborative environment and the customizable database as illustrated by these two examples:
- “CATDocument” /”CATIADocument” classes are replaced by other patterns.
- To create data, you need to get the mandatory attributes set the customer company has decided to have; if you’re a partner, your code should be customization neutral.
Some other changes in the C++ APIs are architecture-related. In such cases, there is almost always a one-to-one mapping and we have tools to help with adoption, for instance:
- Geometric modeler encapsulation allows building smaller products such as 3D Live.
- Separating “Standard” APIs from the “Extend” APIs
Adoption patterns for CATIA V5 APIs are documented in both the C++ and Automation V6 encyclopedia in the “V6 adoption” section. The Automation encyclopedia is part of any Version 6 CATIA installation (DSYAutomation.chm file). An automated tool to audit V5 code is available, allowing Version 6 adoption project feasibility and sizing evaluation. It is recommended to run this tool on the V5R20 code. Trainings for Version 6 adoption are also available.
DELMIA: WE RECENTLY READ ABOUT THE INTERCIM ACQUISITION – WHAT DOES IT MEAN?
INTERCIM provides software to help customers in advanced and highly regulated industries scale up their operations to the next level of productivity with real-time online Manufacturing Operations Management (MOM) and Predictive Analytics for Discovery, Design, Manufacturing and Operations. INTERCIM enables production engineers, workers, inspectors and the supply network to better define manufacturing processes, execute Intercim orders, manage non-conformance and ensure quality. Real-time control and intelligence on Manufacturing Operations over multiple plants help INTERCIM customers achieve their Lean Manufacturing goals quicker and accelerate time-to-market.
DS bought Intercim as a strategic move to increase the PLM reach into new Shop floor communities, to extend PLM as a mission critical driver of manufacturing performance and to increase the value we create at customers.
CATIA: ARE YOU INVESTIGATING RETURNING TO A “STAND ALONE” CAD TOOL WITH CONCURRENT USER LICENSES?
The stand alone solution is CATIA V5 and as mentioned in one of the previous question, we are supporting and continually improving CATIA V5 and will continue to do so for a long time.
SIMULIA: ARE ANY ADVANCES IN COMPOSITE ANALYSIS PLANNED?
In V5 analysis specifically (R20 SP4), we greatly enhanced the composites capabilities by supporting CPD composites properties for nonlinear analysis (Abaqus for CATIA V5 and ANL). This is a valuable enhancement, especially because composite structures often experience large displacements and rotations where nonlinear analysis is very important. There are plans to further improve upon the work we introduced in R20 SP4.
More broadly, SIMULIA continues to build upon its powerful composites capabilities in the Abaqus Unified FEA product line. In recent years we have become a leader in composites analysis through cutting-edge enhancements in crack modeling through commercializing the VCCT (virtual crack closure technique), cohesion modeling, damage modeling, modeling of crushing of composites, and a number of mapping techniques to bring “as-manufactured” shapes and properties into analysis. All of these efforts are ongoing and continue to accelerate, and we continuously look to our customers for requirements to drive future product development.
3DVIA: DOES DASSAULT HAVE A GO FORWARD SOLUTION TO COMPETE WITH OTHER CAD SUPPLIERS IN THE AREA OF TECHNICAL DOCUMENTATION?
• For instance ptc has arbortext, i hear but cannot verify that siemens ug (nx) is working with parallel graphics; what is ds is offering?
• In particular, will ds provide technical documentation support of the s1000d standard, including use of enovia as the csdb for the data modules specified by s1000d?
The heart of Dassault Systèmes PLM 2.0 strategy is "3D For All," and central to this vision is the 3DVIA brand, which extends 3D technology to new users, businesses, and consumers. 3DVIA enables these users to leverage data and business processes from ENOVIA, CATIA, SolidWorks, DELMIA, Exalead, and 3DSwym, to establish entirely new forms of communication, teaching, learning, and consumer engagement.
Interactive 3D technical communications produced by 3DVIA Composer help companies to better explain their products, with one of the primary use cases involving the generation of content for technical publications. With regard to supporting S1000D, 3DVIA Composer already supports the generation of S1000D compliant CGM (as described in Chapter 7.3.2 CSDB Objects – Graphics (S1000D issue 4.0), including the XML companion file support, metafile version 4). 3DVIA is represented at the S1000D Graphics Working Group for Multimedia , and takes into serious consideration any recommendations issued from that group. The 3DVIA Composer native 3D formats are also included in the schemas defined in the S1000D specification (Multimedia Chapter 7.3.3 CSDB objects (S1000D issue 4.0)). It is worthy to note that S1000D is a document-driven strategy that defines the delivery of 2D documents with text linking to images or 3D models. Our “3D for all” approach is to leverage 3D as a way to deliver interactive and self-contained communications, and this usage is not currently defined by the S1000D standard. We are working with major customers and the S1000D multi-media council to help enhance this current standard.
There are plans to integrate 3DVIA Composer and ENOVIA V6 as a platform to deliver interactive and generative 3D Technical Publications centered any 3D CAD content, including CATIA V5 and CATIA V6. This will include the use of ENOVIA as the Common Source Database for the data modules, the main repository for integrated 3DVIA Composer content, the system to manage the desired publication structure and linked objects, and the workflows to drive the generative output of technical publications.
3DVIA: WHAT IS DS'S PLAN FOR SUPPORTING 3DVIA COMPOSER OUTPUT VIEWING USING ACROBAT READER (PDF FORMAT) WITHOUT THE USE OF SPECIAL PLUG-INS?
MANY GOVERNMENT AND LARGE INSTALLATIONS CANNOT ADD NEW APPLICATIONS TO THEIR DESKTOP ENVIRONMENTS, AND PDF IS SOON TO BE AN ISO STANDARD, AS OPPOSED TO BEING OWNED BY A COMPANY (ADOBE).
It’s actually quite easy to publish to directly PDF directly from 3DVIA Composer. With its support for reading and writing to the U3D format, 3DVIA Composer can publish to Acrobat Reader 7.0 or greater without any plug-ins. The default template includes basic views, annotations, BOM tables, etc., and allows you to fully rotate/pan/zoom the model in 3D. Using Adobe Acrobat, PDF templates can also be adapted to deliver custom formatted PDFs.
It is good to point out that, when you use Composer to add interactivity and information into the 3D data, the U3D data format is not robust enough to manage this additional Composer-generated content, and is quite limited in its ability to deliver interactive content.
So, to enhance the Adobe Reader capabilities with better information, better interactivity, and better performance we offer a free plug-in on 3dviacomposer.com to enhance the capabilities of PDF through the 3DVIA Composer Player.
CATIA: WHEN WILL CATIA V5 BE ABLE TO TAKE ADVANTAGE OF MULTIPLE CORE PROCESSORS, ESPECIALLY IN COMPUTING NC TOOLPATHS? SIMULATION AND ANALYSIS? KINEMATICS AND DMU? CORE WORKBENCHES (MD2)?
For Analysis and Simulation, the V5 applications have been taking advantage of multiple core processors for many years (in solver computations). The V5 and Version 6 Visualization component is also taking advantage of two core processors with all V5/Version 6 applications benefitting from multi-core processing for view point manipulation.
In Version 6, major changes were required in terms of architecture in order to support multi-core processing. Version 6 takes advantage of multi-core processing for:
• Machining: parallel processing technology in tool path computation for roughing, sweeping, slope area, contour driven is supported in V6R2011x
• DMU interference algorithms
• Geometric modeler with significant performance gains
CATIA: WHEN WILL A 64-BIT VERSION BE AVAILABLE? WHEN WILL A ‘TRUE MULTI-THREADING’ VERSION BE AVAILABLE?
64-bit is already available and has been for some time, for both V5 and Version 6. All the current V5 and Version 6 releases are taking advantage of 64-bit. A significant number of our customers are using it successfully already.
Regarding multi-threading, we have put in place basic components and are leveraging it on specific processes when applicable. For example, this has been done for interference computation in Version 6.
ENOVIA: WILL DASSAULT SYSTÈMES CONTINUE TO SUPPORT THE SMARTEAM PRODUCT? IF NOT, IS THERE AN END OF LIFE DATE THAT HAS BEEN DETERMINED?
ALSO, WHAT ROLE DOES ARTIZONE REPRESENT IN REGARDS TO SMARTEAM SUPPORT?
DS will continue to support SmarTeam as long as V5 is supported. V5 support will continue for many years. DS has not announced any date for an end of lifecycle of V5.
As a fully DS-owned product, ENOVIA SmarTeam software appears in the DS solutions catalog. V5R20 was released in June 2010 and is scheduled to be followed by V5R21 in 2011. Each release has contained customer driven enhancements and improved design collaboration features, as well as other improvements to maintainability, performance and stability.
Artizone is an R&D partner for DS.
CATIA: WHEN WILL TEXT FUNCTIONALITY BE ADDED AS A STANDARD, AS IN OTHER CAD TOOLS, SO WE DO NOT NEED TO PURCHASE A THIRD PARTY PRODUCT TO EFFECTIVELY MANAGE TEXT IN MODELS? (WHEN WILL TEXT FEATURES BE ADDED AS A STANDARD SELECTION IN SKETCHER (SIMILAR TO PRO/E)?
The 1st drop of 3D text geometry creation from any fonts as simple text definition will be delivered in V6R2012. Text will be available for downstream applications. It can be re-used for embossing or engraving 3D geometry and for Boolean operations from 3D Text creation.
CATIA: WHEN WILL THE CAPABILITY BE AVAILABLE TO ADD UNIQUE ASSEMBLY FEATURES IN A CATPRODUCT THAT DO NOT SEPARATELY MODIFY THE INDIVIDUAL CATPARTS?
Version 6 introduces a new way of managing assembly representation, which simplifies the existing V5 methodologies to answer this request. We are still willing to develop the Assembly Feature on Instance to make it more efficient in Version 6. This is under study for future releases.
ENOVIA: WILL DS PUBLISH A SPECIFIC METHOD (MIGRATION) PATH IN ORDER TO HELP THEIR CUSTOMERS TO MIGRATE FROM ENOVIA SMARTEAM TO ENOVIA V6? (ESPECIALLY FOR SOME MULTI-SITE INFRASTRUCTURE COMPANIES)
DS proposes two approaches to our SmarTeam customers who are considering moving to V6: MIGRATE or COEXIST.
The co-existence strategy is a transitory state with the primary advantage of introducing the V6 technology in a more flexible and non-disruptive manner. The co-existence strategy uses two different approaches:
• Co-existence at the design level engages V5 and V6 solutions in parallel. The new work is performed in V6 while data managed in V5 remains the same.
• Co-existence at the process level means that some new business processes are implemented in V6, in conjunction with the SmarTeam V5 implementation. Bill of Material (BOM) Management and Program Management are examples. These processes will view the V5 data managed in SmarTeam as needed but will not upload or upgrade the data.
DS will provide a variety of technical tools and the necessary mechanisms so that the exchange of the useful data from the legacy V5 system to the new V6 system can be implemented as needed by the Coexist or Migrate strategy chosen by the customer.
ENOVIA: IN AN ENOVIA (MATRIXONE) MULTI-JVM (JAVA VIRTUAL MACHINE) LOAD SHARING ENVIRONMENT, WHAT IS THE BEST PRACTICES SOLUTION FOR SYNCHRONIZING SETTINGS OR ROLL UPDATES MADE BY AN ADMIN TO AN ENOVIA ACCOUNT ON ONE JVM SO THAT THOSE SAME UPDATES WILL BE IN EFFECT WHEN THE USER LOGS BACK IN TO THE SYSTEM ON ANY JVM?
- Parameters in the database (JPO for business logic, data model schemas, P&O, policies) are automatically synchronized on all JVMs.
- For pages (JSPs), the WAR file should be first reconstructed, then it must be copied/deployed on all JVMs
SIMULIA: WILL THE SLM PRODUCT REQUIRE IMPLEMENTATION OF ENOVIA V6 AND CATIA V6, OR WILL IT WORK WITH OTHER PLM SYSTEMS, SUCH AS ENOVIA SMARTEAM, ENOVIA LCA, ENOVIA VPM, ENOVIA MATRIXONE, WINDCHILL, OR TEAMCENTER?
The next-generation SIMULIA SLM products are built completely on the V6 architecture. They use the ENOVIA V6 PLM system, and derive a great deal of benefit from being so integrated with V6. Additionally, SIMULIA SLM works great with other PLM systems, like the ones mentioned in the question. One of the fundamental missions of SIMULIA SLM is to capture and automate simulation processes, which naturally require running both DS and non-DS applications and working with both V6 and non-V6 data sources.
ENOVIA: HOW WILL ENOVIA MATRIXONE WORK WITH ENOVIA LCA, AS FAR AS MIGRATING DATA FROM ENOVIA LCA TO ENOVIA MATRIXONE?
Dassault Systèmes is delivering capabilities and tools to support a flexible migration and coexistence strategy. With the combination of these capabilities, tools and the customer specific business process needs, they have the choice to carry over CAD data and metadata to CATIA/ENOVIA V6 or work in a hybrid V5-V6 environment supporting both design and BOM scenarios.
CATIA: WHY ARE THE KNOWLEDGE PRODUCTS (KBE LINE OF PRODUCTS) “STAGNANT” -- ARE THERE ANY MAJOR DEVELOPMENTS IN WORK?
We must separate the V5 and the Version 6 product lines. It is true that in V5, we have not delivered new functionalities recently and that we are not planning to do so. Regarding V6, we have brought major enhancements to almost all our products and this dynamic will continue. In particular, we plan to integrate a high level knowledge-based modeling language in our V6 solution soon.
ENOVIA: WHAT IS PLANNED TO ADDRESS THE GAPS IN MANAGEMENT OF “OBSOLETE” SPECS IN ENOVIA?
CURRENT, THRU V6R2011X, NO STRATEGIES ARE IN PLACE TO ADDRESS THE SPECIFICATION AND DOCUMENTATION LIFECYCLE PAST “RELEASE”, LEAVING A HUGE HOLE FROM A CONFIGURATION AND DATA MANAGEMENT POINT OF VIEW. THESE LIFECYCLE STATES SHOULD INCLUDE INACTIVE, CANCELED, SUPERSEDED AND OBSOLETE.
1. I agree that many customers do have business process that is linked to Document maturity after Release
a. We can certainly consider adding an additional state to track this behavior. There is no one way that all customers do this
b. This has never been a critical problem in the past
2. Typically, customers that are interested in post release lifecycle, take one of the two following approaches:
a. They add their specific policy states after Release
b. Or, they define a unique policy that is used for post Release tracking
CATIA: IS DASSAULT SYSTEMES CREATING OR MODIFYING THE SOFTWARE TO ALLOW MULTI SHEET 2D DRAWING RELEASES WITHIN ONE .CATDRAWING? IS DASSAULT SYSEMES WORKING TO IMPROVE THE END PRODUCT QUALITY AND SIMPLIFY THE CONVERSION PROCESS FROM V4 MODELS TO V5?
A CATDrawing is only linked to one unique release and we are not willing to open multi-releases sheets inside the same CATDrawing. In terms of conversion quality, we need more detail about this request as 100% is able to be converted as pure graphical result.