Data Sync Manager helps Capita reduce costs

My name's Gary Jackson. I'm the founder of Aliter Consulting, a niche SAP technical consultancy focused on migrations and implementations of SAP on Azure. I've been working with Capita for the past three years on their S/4 implementation into Azure. They were quite used to just doing full system copies and then they ended up with many many copies of production all four terabytes in size. That process was quite lengthy, took a lot of time to actually do a system copy, so they needed to look at an option of having leaner systems and making the whole process a little bit more streamlined if you like. Most definitely saved them time. The Basis team were often spending one or two weeks provisioning or doing a data refresh or a system copy of a system, and then there were a lot of replaying of transports into that system, a lot of the post copy activities. Whereas with Data Sync Manager, you're only refreshing the data, so you're removing a lot of those mundane Basis tasks. So they were able to reduce their storage cost dramatically in their non-production environments, and they were able to spin up additional systems quickly when they moved to the cloud, and then use Data Sync Manager System Builder to make that provisioning process slicker, if you like, more streamlined.

Working with Capita on their S/4 implementation to Azure, they used to do full system copies and ended up with many large copies of Production. They needed leaner copies and to make the process more streamlined. EPI-USE Labs helps save time with data refreshes, system copies, transporting systems, and other post copy activities. With Data Sync Manager you are only refreshing the data, so you are removing a lot of those mundane Basis tasks, and enabling a dramatic reduction in storage costs in non-production environments. Also, it allowed them to spin up additional systems quickly when moving to the cloud, using Data Sync Manager to make the process slicker.

Gary Jackson, Aliter Consulting