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.

Why are non-part BOM Items limited to Professional and Enterprise users?

StephenGStephenG Member Posts: 339 ✭✭✭
I do not understand why Free and Standard user do not have access to BOM Item functionality.

I can understand why Professional and Enterprise subscriptions might have additional functionality to manage items within OS, but there should be some limited functionality for the lower classes.

Are Free and Standard users expected to use the external application OpenBOM to manage non-part BOM items? 

Answers

  • john_mcclaryjohn_mcclary Member, Developers Posts: 3,544 PRO
    Because they needed to store the non part information in a place that multiple users can access / edit.

    The best place was the company container, which is a professional or greater account.

    if every user could have their own library, but then it would be very confusing with so many independent libraries on a company level
  • StephenGStephenG Member Posts: 339 ✭✭✭
    Why couldn't a OS document be that container?

    I see no reason why another DB format needs to be used that is radically different from an existing OS document, something that is only accessible to Professional and Enterprise users. BOM items should be just another data (element) type that can be created within an OS document. The toolbar for such an element type would support creation/management of BOM items.

    I see no reason to restrict users from creating their own BOM items, however, I do see a need to restrict creation of BOM items at the Professional/Enterprise level to enforce usage standards and protocols. From what I know, existing OS document access controls should be adequate in most cases to control management of "official" documents (libraries) containing BOM items.

    It appears OpenBOM would be a better solution, but you need to have an OpenBOM Professional/Enterprise paid subscription to get OS BOM integration. That makes it a No-Go for me. I did take a peak at the "14-Day Trial" and it appears that OpenBOM is really intended to completely replace OS BOM functionality where the BOM info no longer is managed within the parent CAD system, or appears in classic 2D engineering drawings documents. Essentially, the product BOM is completely managed/accessed though a different external DB application. OpenBOM integration appears to be one-way in that one can upload/update (contribute) OS BOM info into a more complete/comprehensive BOM that supports a broader range of usage within an enterprise.

    There is strong augment that BOMs should be created and managed using an application that is specifically designed for that purpose; doing it and having a BOM appear on the face of a drawing is archaic, and inefficient. My needs are simple and I do not need that level of functionality, however, as a Free user I do want the capability to add non-geometric items to an assembly BOM.
      
Sign In or Register to comment.