Addressed by Panelist Jonathan Gable
ANSWER: Starting with V6R2009x we have delivered a set of technologies and tools to help customers move to V6. Our objective is to ease the transition to V6 as much as possible. We offer two scenarios; migration (one shot and incremental) and coexistence.
Coexistence can be implemented at two levels. The first level is focused on the orchestration of design activities with the enterprise configuration management and bill-of-material management business processes. This is available for VPM V4 and VPM V5 customers.
The second level is focused on design data exchange. It gives the ability for customers to keep their existing V4/V5 implementation while exchanging design data with CATIA V6. Designers using CATIA V6 and CATIA V4/V5 can exchange design contexts, modify their design, and eventually update the whole product context accordingly. This is available today for all customers wherever they are working in file-based mode, using ENOVIA SmarTeam V5, Designer Central, VPMV5 and VPMV4.
ANSWER: Starting with V6R2009x we have delivered a set of technologies and tools to help customers move to V6. Our objective is to ease the transition to V6 as much as possible. We offer two scenarios; migration (one shot and incremental) and coexistence.
Coexistence can be implemented at two levels. The first level is focused on the orchestration of design activities with the enterprise configuration management and bill-of-material management business processes. This is available for VPM V4 and VPM V5 customers.
The second level is focused on design data exchange. It gives the ability for customers to keep their existing V4/V5 implementation while exchanging design data with CATIA V6. Designers using CATIA V6 and CATIA V4/V5 can exchange design contexts, modify their design, and eventually update the whole product context accordingly. This is available today for all customers wherever they are working in file-based mode, using ENOVIA SmarTeam V5, Designer Central, VPMV5 and VPMV4.