Announcement

Collapse
No announcement yet.

Solid Edge to Revit?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Solid Edge to Revit?

    I have an equipment manufacturer that does all of their drawings in Solid Edge. Anybody know if I can easily convert this into Revit so I can schedule the equipment?

    I've never used Solid Edge before, so I'm clueless.
    Dan

    #2
    There are no Magic Content Conversion tools, and even the ones from Inventor to Revit sort of stink. You can plop them in to Families using CAD intermediate file extensions (Export his content to 3d dwg and import it in to a family as a static model thats not parametric) but i wouldnt. They absolutely are horrible like that.

    You have to manage materials by layer, and they drag the model down to a crawl, as well as cause instability issues. If it was me, id make a parametric Cube, and use that as a generic placeholder before i would mess around with CAD imports in families.
    Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
    @Web | @Twitter | @LinkedIn | @Email

    Comment


      #3
      So I'd be better off in the long run to create my own native Revit families? That's what I figured. I thought I'd ask before taking on that task and pushing my template creation even further down the list. lol
      Dan

      Comment


        #4
        Originally posted by Twiceroadsfool View Post
        There are no Magic Content Conversion tools, and even the ones from Inventor to Revit sort of stink.
        Was interested in this comment as we are currently weighing up weather to use Inventors AEC Exchange to create our BIM content or create them natively in Revit. I understand content creaed through Inventor is static, but we manufacturer taps and drains which are static anyway. besides the fact that the .RFA files produced are static and possible of larger file size, are there any other disadvantages of creating content through adsk file formats produced by Inventor?

        Comment


          #5
          I suppose it depends on who you ask, and what theyre needs and requirements are. There may be some validity in it, if youre actually using the Inventor files for something else, but i can say that (just my humble opinion), if i have to pick between an overly accurate static model done through ADSK from Inventor, or a pretty generic "box" thats the same maximum dimension out-to-out, modeled in revit... I dont have a very good case for using the ADSK.

          They behave (in Revit, anyway) like imported CAD geometry, from what ive seen.

          If its not created yet (the content), then who is your target audience or end user? If its Revit users, id build it in revit. But, the API gets stronger every year, and ive seen a few promising pieces of software going through IFC. But right now, even the best of them either paths to nativ RFA files, or creates somewhat-okay geometry in an in-place family. I havent seen anything other than native rfa that ill use yet, with the RARE exception being rendering, where ill import cars in to a 3rd file, to be thrown out later.
          Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
          @Web | @Twitter | @LinkedIn | @Email

          Comment


            #6
            thanks for the reply, yeh its really tough decision for our company to make. We are creating the content for use in Revit architecture and MEP. We currently model in Solidworks, it would be highly valuable to have the content created in Solidworks and then using Inventor to create the adsk files for revit as we do use the Solidworks files for manufacturing puposes. basically doing it this way would be killing 2 birds with 1 stone.

            But as you said,
            I havent seen anything other than native rfa that ill use yet
            , which really worries my about choosing this path. I have talked to many hydrolic consultants and architects all who have little knowledge of content creation and adsk, but the ones who do are giving back extremely mixed replies on the validity of adsk...

            it seems autodesk is really skrewing us with not allowing parametric models to be imported into revit. using inventor to dumb down the model using shrinkwrap to a dumb solid, then exporting as adsk with connectors etc, why specifically would this be unusable in Revit say for example a tap?

            Comment


              #7
              It has nothing to do with it being a dumbed down solid, and everything to do with it not being native revit geometry. I cant give you a technical explanation of why, since im not s software programmer, but i can tell you this:

              Imported geometry (versus native Revit geometry), will verifiably:

              1. Cause more instability (fatal errors, randomg crashing, "an error has occurred while drawing the contents of this window, etc)
              2. Cause intense file slowdown / graphical performance lag

              Expanding on this, i have a few files that suddenly exhibit completely bizarre behavior like "this view will print, that one wont," and through the process of elimination, i can isolate a relationship to those problems and revit content built with Imported Objects.

              3. Cause slower view regenerations in addition to overall file slugishness
              4. Become a major PITA to manage the rendering potential through Imported Objects

              Also, i dont work in Revit MEP each day... But so far from the view times i HAVE been in, depending on what kinds of devices you are making... Many of the connectors are pretty parametric, to account for various angles of pipes, ducts, etc.

              <shrug> But were just one office. Imported object = deleted.
              Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
              @Web | @Twitter | @LinkedIn | @Email

              Comment


                #8
                Hey, thanks again so much for your input.
                You seem to have confirmed what i was fearing and that is the software isnt there yet. its close, but its just not worth the risk. looks like we will have to create products natively in Revit and in Solidworks. Its interesting that one of the companies that offer content creation that i spoke to actually use Inventor to create there content... looks like they might have a few unhappy customers in the future.

                Thanks anyway

                Comment


                  #9
                  Originally posted by Twiceroadsfool View Post
                  I suppose it depends on who you ask, and what theyre needs and requirements are. There may be some validity in it, if youre actually using the Inventor files for something else, but i can say that (just my humble opinion), if i have to pick between an overly accurate static model done through ADSK from Inventor, or a pretty generic "box" thats the same maximum dimension out-to-out, modeled in revit... I dont have a very good case for using the ADSK.
                  I think the use caes is more about MEP types of content. The ADSK brings over a really simple model of the geometry but it will carry MEP connectors as well. So you can have a chiller for example created in Inventor and then bring it into Revit via ADSK and connect all of your system pipes to it. If you are just after clearances and tolerances for some "object" the basic parametric proxy box will probably sereve you better.
                  Jeff Hanson
                  Sr. Subject Matter Expert
                  Autodesk, Revit - User Experience

                  Comment


                    #10
                    A TON of manufacturers are doing that. Thats why we dont download their content, LOL.
                    Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
                    @Web | @Twitter | @LinkedIn | @Email

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X