Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. Be respectful, on topic and if you see a problem, Flag it.

If you would like to contact our Community Manager personally, feel free to send a private message or an email.

Piping / Plant Layout Construction / Drawings

Piping and tubing layouts, How do I create piping and tubing layouts? Eg; Plant layout. 
Is it going back to old days, sweeping profiles and no smarts? Or 
Have onshape developed some sort of piping system?

Answers

  • john_mcclaryjohn_mcclary Member, Developers Posts: 3,938 PRO
    edited April 2017
    I know there is a wiring featurescript that onshape manages.
    but I'm not sure about pipe, you will need to browse the featurescripts for one that works for you

    featurescript-beams would probably be just perfect actually..
    https://cad.onshape.com/documents/57fbcb671d998310d4b2fca6/w/06a1f0d4e2106fdc398cf44f/e/2b74655fa0a8717f1991fd52

    otherwise, yes, just sweep profiles as you would
  • philip_thomasphilip_thomas Member, Moderator, Onshape Employees, Developers Posts: 1,381
    Check out The 'Beams' custom feature. This will place pipe on sketch entities.
    Watch the webinar to see how to add your own pipe sections.
    For flanges/weld-o-lets/valves/reducers etc, create your own library (one part per doc - reduces 'new version' notifications) and add explicit mate connectors so that you can use 'snap mating' to build the assemblies very quickly.
     
    Philip Thomas - Onshape
  • ethan_keller924ethan_keller924 Member, csevp Posts: 42 PRO
    @philip_thomas
    Why should a library be one part per doc? 
  • philip_thomasphilip_thomas Member, Moderator, Onshape Employees, Developers Posts: 1,381
    @ethan_keller348 - This was (until recently) our standard advice.
    The reason was that if you added a new part to your 'standard parts doc' (SPD), you had to version the document in order to make the newly added part available to your company users. When you did this, every element that referenced any part from older versions of the SPD, was now marked as 'out of date' (even though it wasn't).

    With the availability of Release Management - two major things changed;

    1) The ability to release individual parts meant that this problem just disappeared - simply reference the revision of the part when inserting (default is latest). Now you are only notified of newer revisions of that part.

    2) The ability to 'non-rev manage' individual parts removes even the obligation to name a revision when inserting a standard part.

    So, if you're not using release management, the old admonishment is the best advice - if you are using release management, this is a non issue.

    I hope this helps :)
    Philip Thomas - Onshape
Sign In or Register to comment.