Export BOM to ERP System

[verge]

Anyone have any experience with exporting a BOM from Pro-E to an ERP system? The company I work for is implementing Epicor as our new ERP system, and we'd like to be able to export BOMs from Pro-E to Epicor. By the time Epicor is fully implemented, we'll probably be using a data management program for our Pro-E files - we're leaning towards DDM.


Can anyone give me any info on this?

 

[BigD]

I think a PDM system is essential for getting BOMs out to the rest of the business. I've spoken to some software developers re exporting BOMs from DDM. The ERP system we are looking at runs on SQL server too, so they suggested creating some software that looks at the DDM database every so often, picks up the necessary info and populates the ERP database. This was rather than using the built in EUM function in DDM.

Once we've done this I will post the results!

 

[verge]

That would be great. Thanks. I'm trying to convince management here to go with a PDM for all users(leaning towards DDM), but they don't want to make the investment at this point in time. They are willing, though, to install one or two seats. I'm thinking this may be all right for exporting BOMs, but we may have some major problems on our hands as far as access control goes.


I'd love to hear how your experiment works out. I'm always willing to let someone else play the guinea pig.

 

[kevinjbrault]

Iam going to take the "counter-point" of BigD. The PDM system gets the BOM from the ProE model. Thus the PDM system is just one more step that adds complexity and can cause error.


We have not had the best success transferring the data from one database to another (e.g. Intralink Oracle to SAP Oracle). There are too many innuendos that are easily broken when you upgrade either package and, believe me or not, regardless of how much due diligence is done, the data on the drawing, at times, will not sync with the BOM in Intralink/PDMLink. This is because someone will always try a short cut regardless of the training you give them. Someone needs to review the BOM against the drawing beforeeither gets released (now this may happen in the ERP system).


Furthermore we have seen (once again ... believe me or not) Intralink BOM functionalitychange when ProE is updated or Intralink is updated. So be forewarned if you do not review your BOM's before release, you may have discrepancies.


What we have been successful with is taking the data management out of the equation. When a drawing to promoted in the PDMLink or Intralink a trigger is executed that starts ProE and creates the drawing PDF and exports the BOM from ProE. Then both of these files are pushed into the ECO release system and get reviewed together. If they don't match it is caught before the print or BOM is released.


This method also works even if you do not use a PDM system for your ProE data. The user hits a mapkey that creates the BOM, a zip backup of the drawing and ProE data and a PDF file. All three move through the ECR process and if approved get vaulted.


In the early days of Intralink we had so much trouble retrieving old revisions from Intralink that we developed the "ProE backup" method. And we still use it today at some sites because it will give you the exact reproduction of the ProE data that was used to release the drawing and is easier for the users to understand and use.


I some of you find this useful.

 

[verge]

Kevin,


Definitely useful. We're in the process of doing everything at once - implementing Pro-E, implementing an ERP system, renaming tons of parts, and just getting into routings, etc. Of course, at the same time, our business has gone through the roof; we're amazingly busy. Any and all information at this time is useful.


There will be an awful lot of reviewing and analysis before we've hit on a solution - I'm simply trying to pitch in and help make things as "user-friendly" as possible. Our one advantage is that we're not building incredibly complex machines, so our BOMs are short and simple as compared to many other businesses.


I like the Pro-E backup concept. That will probably be something we'll do at least for a while until we feel we can trust our new system (that will be a long while, it looks to me).


Thanks for the input.

 

[kevinjbrault]

We have some tutorials on our website http://www.stdg.us/Administration.htm


Let me know if we can help.


Kevin

 

[verge]

You're doing some fascinating stuff. I'm pretty much a CAD newbie in comparison to this kind of advanced work. What you're saying about releasing BOMs is obviously very well thought-out. We need a data management system for many reasons (parts numbering, access control, revision control, etc.), but we're still figuring out the BOM export.


One question - do you work with really complex assemblies? A lot of revisions? We're not a manufacturing environment - we're building portable power generation units (well, they're portable if you own a tractor/trailer). On the mechanical side, we're mainly assembling other manufacturer's parts, although we do have a sheet metal shop and build door assemblies and the like. So our revisions don't come fast and furious - if someone misses one, it's because they were asleep or something.


It'll be a long road to a decision, especially with so much work on our hands.


I will be spending my lunch time looking through your information (speaking of which)...


Thanks again.

 

[kevinjbrault]

We do alot of large assemblies of simple parts (automated equipment) and some small assemblies of complicated parts (cell phones).


Go ahead and give me a call using the phone number from the "Contact" tab on the website.