COE2010 Razorleaf ENOVIA SmarTeam and V6 Readiness


Published on

Published in: Education
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • V6 Readiness is more than a state of deployment or of software configuration, it is a thought process or a thinking of the end game… ENOVIA V6.For clients currently using CATIA V5 who may be considering migrating (this is not an upgrade) to CATIA V6, consideration for timing and external forces (OEM, supplier, client forcing the migration to V6 for compliance) may determine your starting point.The concept of V6 Readiness (especially for this presentation) was originally a SmarTeam concept that implied a methodical progression of upgrades/migrations to get the client into more of a V6 orientation. For instance, CATIA V5 managed by SmarTeam V5, using the PLMDB data model, employing the Express mechanisms and methodologies, accessed through the 3DLive experience would orient the client to be better prepared to migrate to V6.Becoming V6 Ready can have many starting points. From a CAD-only (CATIA) deployment, to a legacy SmarTeam or newer SmarTeam deployment or even a new deployment on V6 PLM Express. Every client will begin the journey to V6 from a unique point, but most will end up at V6 or perhaps as a co-existence deployment.
  • V6 Readiness is more than just terminology, licenses, software, etc. It’s a methodology. The methodology takes into account things like CAD platform, data model, customizations, user interface and more.Because V6 Readiness is a methodology, it enables you to plan. When was the last time someone asked you to look out 18 to 36 months and describe where your PLM strategy would be and how much that might cost? By employing V6 Readiness principles you can plan the steps and estimate costs fairly accurately enabling you to plan and execute a V6 deployment plan.Along the way there will be benefits of becoming V6 Ready that you can take advantage of in order to improve business. Imagine that. Putting together a 24 month deployment plan that has incremental benefits, not just benefit at the end.V6 Readiness will also orient the business in a V6 way since the V6 Ready principles demand it. This will relieve some of the cultural changes that will be necessary to have a successful V6 deployment.I hate to say it, but for once, a vendor’s claim of “readiness” just seems to make sense. At least it makes sense to me. The data model, the express behavior, the orientation, the tools. It just feels right. Things like Design Express (read as Design Central in V6) and Engineering Express (read as Engineering Central in V6) just… makes sense.
  • Getting to V6 is really a journey and the journey really depends on where you start. Is only CATIA V5 deployed, without PDM? Are you using Matrix with CATIA V5? The path you will take will be influenced by where you’re at and where you want to end up.This slide represents several starting points and is flavored by this event (COE).Some of the paths have been articulated by Dassault while others are more ambiguous or obscure. The following diagrams attempt to tell the story of the journey.
  • NOTE: the red dot signifies deployment of 3DLive.CATIA V5 with No PDMThis journey to V6 is one of the more direct and articulated paths. Although migrating to V6 HE is an option, if your deployment calls for PLM Express functionality, simply adding SmarTeam CPE then 3DLive results in V6 Readiness. Migration to V6 CPE (PLM Express).CATIA V5 + SmarTeam CPE + 3DLive = V6 CPE Readiness
  • As with the previous slide, CATIA V5 with PLMDB (CPE – CATIA PLM Express) is a direct route to V6 CPE.
  • CATIA V5 with SmDemo VariantNow things start to get a little interesting. Depending on the data model, legacy data and add-ons in use (WFL, BOM, PGM) this journey can be direct to a bit fuzzy.A CATIA V5 with out-of-the-box (OOTB) SmarTeam with SmDemo with little or no customizations has the most direct migration to V6 CPE.If no add-ons are in play and there has been some customizations to the data model or scripting, a migration to PLMDB and express methodology is in order. If add-ons are in use such as Workflow (WFL) and Bill of Material (BOM) then a data migration to PLMDB is in order and even then the WFL and BOM portions are a little hazy in getting to V6. Dassault has stated they have or there will be tools but the solution is undefined. For sure, consulting services will be required.CATIA V5 + SmarTeam SmDemo + Data Migration (PLMDB) + 3DLive = V6 Readiness
  • CATIA V5 with PLMDB and WFL/BOMAlthough this seems like a direct route, migration of CATIA V5 CPE with WFL/BOM has not been detailed by Dassault.
  • CATIA V5 with MatrixIf your environment is Matrix with CATIA V5 then a migration or upgrade to ENOVIA V6 is the ticket to V6. Although we will not talk technically about this scenario, there is methodology at this time for upgrading Matrix to EV6. It is unknown if there are tools to do the migration and the migration to V6 HE VPM is a little fuzzy.
  • CATIA V5 with VPMAlthough it seems like a simply matter to migrate to V6 HE with VPM, the tools, plans, methodologies etc, have not been detailed by Dassault. Again, this topic is beyond the scope of this presentation, but it should be mentioned nonetheless.
  • V6 (not sure whether this is CPE or HE) with xCAD. The migration is really fuzzy at this time.This migration is probably the most complex simply because of the xCAD and SmDemo factors. This deployment is typically a legacy SmarTeam deployment that has many CAD integrations or old CAD integrations. There is a lot of data, links, customizations, migrations, you name it to be considered.BUT, there is a V6 xCAD destination that could make the journey straight forward if the deployment was OOTB SmDemo with little customization.
  • The V6 Transition can happen in a couple ways: migration or coexistence. Migration means that V6 will be implemented and the V5 data will be migrated. The migration effort (level of automation) is related to the amount of customization or how “V6 Ready” a deployment is at the moment of migration. Coexistence essentially means that legacy design will be maintained in V5 while new design or new applications will be maintained in V6.An example of coexistence might be a V5 deployment that really has a need for Material Compliance in V6. V6 can be deployed and the Material Compliance application can be used while the V5 environment continues to be used, too. Likewise, there may be a need to maintain the V5 design environment, but new projects can be completed in V6. This calls for a coexistence methodology.There are tools available that enable migration to happen on the fly. Essentially, the data is searched for in V5 and migrated to V6, right now. Of course, the fewer the customizations the greater the use of vendor supplied tools and methodologies in transitioning to V6.The scenarios that were outlined previously do not represent all of the potential scenarios. What about someone on Windchill who wants to migrate to V6? Teamcenter? For sure, patience will be required. If you’re not an early adopter, sit back and a solution may present itself.
  • There are many challenges in the transition from V5 to V6. Some of these challenges are outlined below.Data ModelOf course just about any SmarTeam data model can be migrated to PLMDB and then to V6, but the success of that migration is dependent on the legacy data model and whether the super-classes and classes and their attributes have a suitable location in the PLMDB data model.If a client had deployed SmDemo (or a close variant) it is very likely the data can be migrated to PLMDB without much trouble. On the other hand if a custom data model was created with very different super-class methodology then extensive mapping will need to be planned and there could be data loss to accept.Special Behaviors/ScriptsIf your data model is very old it may have had database mechanisms that are no longer supported or were replaced by newer mechanisms. Usually the data model designer (update) can take care of the situation, but it can get complicated.If your deployment includes a lot of scripts to enable special behaviors that were not part of (or thought of) SmarTeam OOTB, then you’ll need to map those scripted behaviors to a PLMDB methodological behavior (Express behavior) or to a V6 behavior or do without the behavior.WorkflowWorkflow comes up quite a bit when discussion V6 Transition. At this time, the migration of workflow data has not been defined, so how to plan for workflow data is a little fuzzy. To be fair, workflow and the network of links that go with it is very sophisticated and is by no means a trivial migration matter. However, SmDemo to PLMDB migration can take into account workflow because the class structures are similar, or better said, able to be mapped.Regulatory ComplianceRegulatory Compliance (FDA), BOM, PGM and other add-ons to SmarTeam make the V6 Transition a little fuzzy. The reason it gets fuzzy is that the underlying schema and application architectures are very different between SmarTeam and V6. If this legacy data is important to bring forward, be sure to allow for that special planning.Special LinksLike scripts and special behaviors, if you’ve defined your own link types, you’ll need to spend some extra time to map, migrate or dispose of this data.xCADAs expressed earlier xCAD integration data will make the transition a bit more challenging. Most of the integrations supported to SmarTeam exist in V6 but may represent an integration that will change or need to change to be useful for your CAD folks.
  • ExpectationsIf you think you may be migrating to V6, start planning now. It costs very little to start the ball rolling and time is on your side. It was mentioned earlier that you have the ability to plan the transition to V6 and you could spread out the planning (and cost) over 18 to 36 months if you needed to.Don’t try to think about, plan or do this on your own. You’ll spend way more money than if you contracted a good service provider to help you out.Be ready to spend $50k, $100k or even $150k to migrate to a CATIA V5 on PLMDB environment. It breaks down a little like this: Data migration (projects, documents) ~$50k and about two monthsData migration with WFL and/or BOM ~$100-$150k and about 4 monthsThere is deployment, licensing and training that are baked into the estimates as well. Remember, there will be ROI that comes out of this migration. It’s not a wasted event.By all means, think big. Think about the future of your company. Think growth. Think global. Think competitive advantage. As a good friend of mine once told me “Go big or go home.”
  • COE2010 Razorleaf ENOVIA SmarTeam and V6 Readiness

    1. 1. ENOVIA SmarTeam and V6 Readiness<br />Michael Craffey, Razorleaf Corporation<br />
    2. 2. Michael Craffey<br />Principal Consultant with Razorleaf Corporation<br />Over 20 years experience in PLM and CAD<br />
    3. 3. Agenda<br />What is V6 Readiness?<br />Benefits of V6 Readiness<br />From Where to There?<br />V6 Transition<br />Challenges<br />Expectations<br />Q&A<br />
    4. 4. Agenda<br />What is V6 Readiness?<br />Benefits of V6 Readiness<br />From Where to There?<br />V6 Transition<br />Challenges<br />Expectations<br />Q&A<br />
    5. 5. What is V6 Readiness?<br />Begins with the end in mind… ENOVIA V6<br />CATIA V5 thinking of moving to CATIA V6<br />The concept is SmarTeam oriented<br />CATIA V5<br />SmarTeam PLMDB<br />Express Mechanisms/Methodology<br />3DLive<br />Has many starting points<br />
    6. 6. Agenda<br />What is V6 Readiness?<br />Benefits of V6 Readiness<br />From Where to There?<br />V6 Transition<br />Challenges<br />Expectations<br />Q&A<br />
    7. 7. Benefits of V6 Readiness<br />Is actually a methodology to get to V6<br />Enables planning<br />Has (incremental) benefits, not just a method<br />Orients the business toward V6<br />Makes sense<br />
    8. 8. Agenda<br />What is V6 Readiness?<br />Benefits of V6 Readiness<br />From Where to There?<br />V6 Transition<br />Challenges<br />Expectations<br />Q&A<br />
    9. 9. From Where to There?<br />CATIA V5 without PDM<br />CATIA V5 with SmarTeam (PLMDB)<br />CATIA V5 with SmarTeam (SmDemo variant)<br />CATIA V5 with PLMDB with WFL/BOM<br />CATIA V5 with Matrix<br />CATIA V5 with VPM V5<br />xCAD with SmarTeam (any data model)<br />
    10. 10. xCAD<br />SmDemo<br />CATIA V5<br />SmDemo<br />CATIA V5<br />Matrix<br />xCAD<br />PLMDB<br />CATIA V5<br />CPE<br />CATIA V5<br />No PDM<br />CATIA V5<br />VPM<br />V6 CPE<br />CATIA V5<br />CPE<br />WFL/BOM<br />V6 CPE<br />WFL/BOM<br />V6 HE<br />VPM<br />V6 HE<br />CV5<br />V6<br />xCAD<br />
    11. 11. CATIA V5 without PDM<br />CATIA V5<br />CPE<br />CATIA V5<br />No PDM<br />V6 CPE<br />
    12. 12. CATIA V5 with PLMDB<br />CATIA V5<br />CPE<br />V6 CPE<br />
    13. 13. CATIA V5<br />SmDemo<br />CATIA V5<br />CPE<br />V6 CPE<br />CATIA V5<br />CPE<br />WFL/BOM<br />V6 CPE<br />WFL/BOM<br />CATIA V5 with SmDemo Variant<br />
    14. 14. CATIA V5 with PLMDB and WFL/BOM<br />CATIA V5<br />CPE<br />WFL/BOM<br />V6 CPE<br />WFL/BOM<br />
    15. 15. CATIA V5 with Matrix<br />CATIA V5<br />Matrix<br />V6 HE<br />VPM<br />V6 HE<br />CV5<br />
    16. 16. CATIA V5<br />VPM<br />V6 HE<br />VPM<br />CATIA V5 with VPM V5<br />
    17. 17. xCAD<br />SmDemo<br />xCAD<br />PLMDB<br />V6<br />xCAD<br />xCAD with SmDemo Variant<br />
    18. 18. Agenda<br />What is V6 Readiness?<br />Benefits of V6 Readiness<br />From Where to There?<br />V6 Transition<br />Challenges<br />Expectations<br />Q&A<br />
    19. 19. V6 Transition<br />V6 Transition: Migration and Coexistence<br />Migration – Implement V6 migrate V5 data<br />Coexistence – Continue using V5 but start to use V6 applications<br />Can migrate data on the fly, tools exist<br />The more OOTB or “V6 Ready” a deployment, the better the migration tools, 90% automated<br />Not all scenarios have been discovered and thought through, patience is required<br />
    20. 20. Agenda<br />What is V6 Readiness?<br />Benefits of V6 Readiness<br />From Where to There?<br />Methodologies and Tools<br />Challenges<br />Expectations<br />Q&A<br />
    21. 21. Challenges<br />Data Model<br />Special Behaviors/Scripts<br />Workflow<br />Regulatory Compliance and other add-ons<br />Special Links<br />xCAD (multi-CAD)<br />
    22. 22. Agenda<br />What is V6 Readiness?<br />Benefits of V6 Readiness<br />From Where to There?<br />Methodologies and Tools<br />Challenges<br />Expectations<br />Q&A<br />
    23. 23. Expectations<br />Start planning now<br />Get help<br />PLMDB data migration estimates<br />Think big, think future<br />
    24. 24. Agenda<br />What is V6 Readiness?<br />Benefits of V6 Readiness<br />From Where to There?<br />Methodologies and Tools<br />Challenges<br />Expectations<br />Q&A<br />
    25. 25. Michael Craffey<br /><br /><br />@Razorleaf<br />330.676.0022 x7121<br />