Our services for ERP environments
I choose to present my services from a failure perspective. And I have two good reasons to do so. I'm a pragmatic person who likes to place his approach in a real life setting. And secondly, organizations normally look for an ERP architect after their initial approach wasn't successful.
It's just easier to understand the added value of an ERP architect from the failure view. It will probably relate to your past experiences. Do you recognize your storyline?
IT in the lead
IT looks different at daily operations and requirements. Operational resources should be allocated and make decisions, IT and suppliers must support.
Issues: Low organizational adoption, missing ownership, unclear governance, unrealistic testing.
Unclear targets
Unclear targets leads to gaps, rework and overlapping functions. States need to be defined and aligned with all stakeholders.
Issues: Unvalidated business case, scope creep, data quality issues at migration, unnecessary enhancements.
Missing milestones
Without clear intermediate milestones, all status lights will stay green until testing starts. Deliver in cycles and users will learn and grow immediately.
Issues: Unrealistic planning, missing control, budget overruns, change management issues.
Best-of-breed environments
When you implement ERP in a best-of-breed environment, I strongly suggest to develop a central application for data exchange to prevent issues like budget overruns and unnecessary enhancements. But also security, flexibility and application management will benefit.
Data exchange claims a lot of resources from consultants and requires many enhancements in ERP or other applications. If you implement these services in a central platform, you will get control on all your data flows. You can re-use data. And your ERP will be dismissed from any data enhancements. Consultants can focus on their application and necessary dataset. Want to know more?