Replenishment+ is Olivehorse’s chosen Demand Driven MRP solution for several reasons. Here's why..
R+ was the first DDMRP compliant solution and so has benefited from rigorous testing through numerous deployments globally. This means we have a tried, tested and stable solution. It also has the benefit of being incredibly simple and easy to integrate into existing ERP landscapes. Hence, it can run in parallel without having to change any of your existing configuration. This for us is an ideal scenario as it will allow APO/ECC to deliver the benefits of large scale analysis and execution required for mid/long term planning and continue to manage the execution of production recording, distribution management and procurement. At the same time, it means R+ can focus on the core value driver of making it simple and easy to interpret daily replenishment decisions without unnecessary additional requirements of the system.
The segregation of activities means R+ can very easily create a replenishment plan, everyday, in a matter of minutes. Something with a large and complex solution such as APO would never have seemed feasible.
This speed is driven by the simplicity of the decoupling method of DDMRP. There is no need to carry out complex dependent requirement generation from downstream DC all the way to procurement planning any more. Each node is planned independently and therefore can be run independently of each other. This means procurement planning can be performed without needing to wait for confirmation of planned production as production is planned independent of distribution. There is no need to wait to carry out planning sequentially.
What if a plan changes significantly and requires attention? As R+ runs everyday, the changes will be picked up the next day!
Not only is R+ simple, easy to use and fast, the speed of deployment is also rapid. From our previous implementations, we have gone from contract to go-live in 10 weeks. This speed is driven in part by the technology of R+ (being cloud based and thus requiring nothing more than internet access to use) and the simplicity of requirements to use in driving DDMRP.
A 10 week implementation is typically made up of an 8 week preparation period, where systems are setup on the cloud with data extraction methods are agreed and validated. All this is usually carried out by non-operational planners / IT teams. Once the architecture is in place there then follows a 2 week implementation period where planners are trained in DDMRP principles, scope of go-live is agreed, buffers are sized and systems training delivered. Go-live typically takes place in the middle of week 2.
Hopefully you have an insight into why we have chosen R+ and some of it's benefits. In our next blog we will start to explore some of the functionality available, highlighting the key capabilities of: Visual buffer management, Dynamic buffer adjustments, Demand driven alerts and inbuilt reporting.