I have implemented a version of this before. This will require some digging and an open mind. Skirt the periphery when possible where two systems need to talk.
Have you ever considered using Named BOM"s and route them directly inside EPDM to supply chain for ordering (BOM compare on changes), then to warehouse for kitting & disposition, then back to origin for closing?
That might just fix 90% of your issues without a huge impact to operations and a huge financial burden paying a consultant to create you a custom wrapped API add-in.
Identify the root cause of the out of synch data between the systems using the 5Y's.
A few questions:
- On #1 What current part info in purchasing software is changing that needs to update EPDM? Expand please. Do these systems really need to be synchronized or do parts of the data need to be?
- On #2 What new/missing items will there be? Expand please.
- On #3 Not sure this is feasible since you don't own that data and changing data inside a supply chain software is very risky. I honestly would not want that liability looming over my department. Not sure I would recommend that as I have seen this backfire very badly.
- On #4 The best case with this one is putting the data in a neutral zone where the purchasing software can come get it. Again, making changes in supply chain software, not recommended.
- Decide how deeply the systems should "talk" with one another because your organization needs to identify where those business boundaries are going to be.
- That will force you to decide which system "owns" the data.
- The other system is going to "peek" into the "owner" system for updates/synchronization.
- Since EPDM is in your wheelhouse, let it do the peeking. Get this process under your control if you can.
- Fabricate a work process where the equation is "decreased controls" + "increased functionality" = "maximum flexibility"
You "could" write a custom EPDM Task add-in that peeks into Ostendo and updates EPDM on a nightly basis but sometimes the best add-in can be replaced by a better process and I've found that running programs unattended means the data must be sanitized and scrubbed. This may not be the best approach for you but it just might.
Consider the Named BOM's if you haven't. They are powerful and easy to manage.
You may be familiar with it but read "The Goal" by Eliyahu Goldratt - Theory of Constraints: A process of ongoing improvement. Great novel and well written for process minded people like us.
Lastly there are usually two phases:
- Cleanup - Go back and remedy all the out of synch data between the systems OR just draw the line that says as of this date, the process changed and all legacy data will have to remain as is.
- Sustainability - Fix both your work processes and your EPDM processes to align to the new plan
Hope this helps, I'm rambling at this point.
Thanks for your reply, obviously a bit more experienced at it than me!
I have looked at the named BOM set up however due to the large number of parts/assemblies we create, and not enough man power we arrived at the idea of creating an automated process. Depending on the cost, I could possibly be re-visiting this idea.
Regarding your questions:
All the communication process is going to go from EPDM to our purchasing software
- The main info that changes is the revision of the file as changes are made, and the description. The revision must be updated, and this is currently where most of our problems are coming from, old revisions being made instead of the latest.
- New missing items relate to if we have drawn a new part in solidworks, that it should go through and add this to the purchasing software
I also see what you mean by 3/4
Basically the main aim is to reduce the errors that occur, and decrease the wasted time spent by us/storeman in entering duplicate information into purchasing software.
Thanks for your help, good points for me to keep in my mind!