{"id":1080,"date":"2018-03-19T11:40:00","date_gmt":"2018-03-19T18:40:00","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/NX-Design-Blog\/CMM-Migrating-to-NX-From-Catia\/ba-p\/456563"},"modified":"2026-03-26T04:17:08","modified_gmt":"2026-03-26T08:17:08","slug":"cmm-migrating-to-nx-from-catia","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/nx-design\/cmm-migrating-to-nx-from-catia\/","title":{"rendered":"CMM: Migrating to NX From Catia"},"content":{"rendered":"

In this post let\u2019s take a closer look at the particulars around migration data to NX from Catia.<\/P><\/p>\n

First consideration are the CMM settings, as these control the output we\u2019ll have to work with once in NX.  Make sure to go through the CMM settings to make sure the output will be as you expect so you have the best possible staring point.<\/P><\/p>\n

The biggest difference in migrating to NX from Catia versus other CAD systems is the use of Geometric Sets in Catia.  CMM migrates these into Feature Groups into your NX part file.<\/P><\/p>\n

The other key area is the extensive support of Linked Geometry from Catia to NX.  Migration will maintain most of the links created in the Catia file during migration as long as all supporting files are included with the data to be migrated.<\/P><\/p>\n

Featured Migration Result:<\/P>
\n

\"knuckle-featured.jpg\"<\/span><\/P><\/p>\n

B-rep Migration Result:<\/P>
\n

\"knuckle-B-rep.jpg\"<\/span><\/P><\/p>\n

Things to remember:<\/STRONG><\/P>
\n


    \n
  1. CMM creates an NX part file containing Intermediate B-Reps and DAF\u2019s for any failed or unsupported features; and Final B-Rep<\/LI>
    \n
  2. NX part file size
    \n

      \n
    1. Dependent upon CMM options<\/LI>
      \n
    2. Success of migration<\/LI>
      \n<\/OL>
      \n<\/LI>
      \n
    3. Hidden B-Rep and Points
      \n

        \n
      1. Aid in part repair<\/LI>
        \n
      2. Validation of migrated\/repaired part<\/LI>
        \n<\/OL>
        \n<\/LI>
        \n<\/OL>
        \n

        Standard Order of Repair when working with migrated data:<\/STRONG><\/P>
        \n


          \n
        1. Work in Timestamp mode<\/LI>
          \n
        2. Repair features in order from earliest to latest; down the part navigator tree from first to last<\/LI>
          \n
        3. All repairs should duplicate the captured B-Rep body for the failure\/unsupported feature<\/LI>
          \n
        4. The repaired feature needs to be before the captured B-Rep body for the failure\/unsupported feature in the PNT<\/LI>
          \n
        5. Use Replace on the captured B-Rep body for the failure\/unsupported feature with the newly created feature as the replacement feature<\/LI>
          \n
        6. Use Convert to Linked Body on the last B-Rep body in the PNT, edit this to create associativity to the featured model.  This converts the B-Rep body into an Extracted Body after the edit.<\/LI>
          \n<\/OL>
          \n

          In the following avi\u2019s we will look at a Wheel\/Brake Asssembly created in Catia and then the resultant data after CMM in NX.<\/P><\/p>\n

          <\/p>\n

          \n
          <\/div>\n