×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

ERP BOM matching SW BOM

ERP BOM matching SW BOM

ERP BOM matching SW BOM

(OP)
I’m not sure exactly where to post this, but think this is probably going to net me the more correct answers.  I think this has been discussed before, but Search is down.

For those that have an ERP system without PDMworks, how do you maintain your SW models to match your ERP BOMs?  Our general practice is to expire parts that are under change, assign effectively dates for the new revision of the part.  Sometimes, a component (part or assembly) may be replaced with a new component.

BOMs in our ERP system are numbered by 10s.  Meaning a 4 component BOM will have line items designated as 10, 20 30 40.  Sometimes, folks in other departments want to add a new component, perhaps a plastic bag, perhaps a bundle of cable ties, sometimes an install instruction.  Sometimes they add them as Item 50.  That’s perfect, and it’s easy for our folks to update the SW model to add that item.

Sometimes though, folks add a component as Item 5, 15, 25, etc.  That throws everything out of whack.  Everyone has their well-discussed reasons for wanting to add a "half-number" as I call them.  The greatest reason is as a visual indicator that the newly added component is associated with the other (15 is associated with 10).  Let’s face it, if you work in a manufacturing plant, the guys in the shop builds to a BOM, they don’t build to a solid model.

Sometimes, components in a BOM are expired, and the position in the BOM is maintained for archival reasons.  This may make a BOM look like 10, 40, 50, 90.  We’ve been able to manage our models to insert a blank part or assembly file with the title EXPIRED.  This acts as a placeholder in the SW BOM, and it matches our ERP BOM.  Everyone is happy, except for the folks that get stuck having to modify a SW assembly with many expired files.

Looking for any suggestions/work arounds to streamline some of this mess, short of "getting a PDM package."

"Art without engineering is dreaming; Engineering without art is calculating."

Have you read FAQ731-376 to make the best use of Eng-Tips Forums?

RE: ERP BOM matching SW BOM

MadMango,
We use MK which also puts in item numbers as 10, 20, 30 and etc. Our Doc group will not let anyone put in half numbers. Also MK is set up not to be changed, so no one can put in half numbers anyway.

I would ask your ERP developers to make the ERP system not allow half numbers.

Bradley
SolidWorks Professional x64 2007 SP3.0
Intel(R) Pentium(R) D CPU
3.00 GHz, 3.93 GB of RAM
Virtual memory 12577 MB
NVIDIA Quadro FX 3400

RE: ERP BOM matching SW BOM

(OP)
Bradley, your company is the only other one I know that uses MK.  I thought our company was the only one.  We are on release 8.5, what about you?

As I posted above, Sales, Planning, Purchasing, etc have their reasons for wanting the half numbers, so it is a situation that I need to work around.  They have existed since 1997, and they won't go away.

"Art without engineering is dreaming; Engineering without art is calculating."

Have you read FAQ731-376 to make the best use of Eng-Tips Forums?

RE: ERP BOM matching SW BOM

MadMango,

Reading your description of what's going it, it reminded me of old BASIC coding.  3eyes

Something that works for my company is not even bothering with SW BOM's at all.  We use a PLM/MRP system that maintains BOM's, and the SW activity drives none of it automatically.  This works great for us, but I know many systems would have an issue with it.

Matt
CAD Engineer/ECN Analyst
Silicon Valley, CA
http://sw.fcsuper.com/index.php

RE: ERP BOM matching SW BOM

MadMango,
 MK 8.10 9902
Your higher than us, so that means we do not work for the same company.

Bradley
SolidWorks Professional x64 2007 SP3.0
Intel(R) Pentium(R) D CPU
3.00 GHz, 3.93 GB of RAM
Virtual memory 12577 MB
NVIDIA Quadro FX 3400

RE: ERP BOM matching SW BOM

We also drive MRP/ERP externally (ie. excel spreed sheets we create from scratch).  A data entry clerk would import or re-enter our bom information from the excel spreadsheets. We release these spreadsheets as "separate parts lists" for the solidworks assemblies and reference the file name on the drawing.

It is by no means a great system, but it is a lot easier to manipulate an excel spreadsheet than a Solidworks BOM.

If I understand your problem though you want to have your item numbers count by 10's or 5's in your solidwork's assemblies.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources