One common criticism is that even though the overall system may be functional, the integration was a custom-coding nightmare. Another is having to dedicate key programming resources to month-long projects spent punching out single-use code ended up costing tens of thousands of dollars, putting the company at risk.
In other cases, the project team was skilled with underlying protocols, data formats, and plant floor systems but depending on them to also become experts in the SAP development environment was another story altogether.
Staffing integration projects with the right skill sets can be a real problem and getting it wrong creates higher project risk and budget overruns. Often, companies are left in the uncomfortable position of being completely dependent on the outside consultants they hired to do the integration; not to mention the significant impact on their IT budget.
There’s no doubt about it– the above statements are rooted in truth. Many plant floor to SAP integration projects have significant room for improvement. The intent of this document is to explore some alternatives to these statements.
[ctaDown custom_down=”5MythsSAPShortTwoPoint0.pdf” custom_lead_source=”5MythsAboutPlantFloorSAPWhitePaper” custom_head=”Download”]