Implementing a new solution contains, almost by definition, an element of change. The majority of Nobex’s implementation projects have in one way or another been a part of a bigger picture where a client is planning a migration from an older ERP platform to a new one – while balancing cost, risk and load on resources. Typically these are scenarios where the old ERP solution has had legacy functionality built to fulfill warehousing and distribution requirements. These customizations however make upgrades more difficult to manage.
In this context our Supply Chain Broker (SCB) has been a key element in creating a manageable and cost justifiable migration strategy. As there are available SCB adapters for various ERP systems the first step of the migration path consists of implementing a new, highly configurable distribution solution from Manhattan Associates – integrated to the old ERP platform with the SCB via the appropriate SCB adaptor. This enables the client to shrink his ERP system by shutting down the custom WMS functionality and moving users to the new Manhattan solution. This approach also enables multi-site implementations to be phased – with each site going live with the new solution in a more controlled way, rather than with a big-bang approach.
When the new Manhattan distribution solution has been successfully implemented and stabilized and at a time suitable to the client, the task of migrating remaining functionality still supported by the older ERP platform, to a new ERP platform, is much easier. The new ERP system is then integrated to the Manhattan WMS solution by switching ERP adaptors – preserving the investments already made with the new WMS.
As an example Nobex has participated in many projects where clients were migrating either from the older Navigator to Dynamics NAV, or from Concorde XAL to Dynamics AX. All these platforms are open sourced and, especially older, implementations tend to be heavily modified – often with ‘homegrown’ WMS functionality.