Client Copy 속도 향상으로 테스트 개선

My name is Harsha Patel, and I work for BT, British Telecommunications: one of the biggest corporates in the telecoms market. The employee size: we are about hundred thousand people. BT acquired EE as a business about five years ago, and we have a massive EE SAP platform, which runs the core business functions for EE. We look after integration environments, so SAP is a key component of that. Before EPI-USE, we had to do double keying, and so the testers were putting in some of the data, and then there was a Production team putting it into Production, and there were mismatches between what they were putting in. That would lead to production faults because it wouldn't quite match what the testers were putting in. So they might correct things, but then it wouldn't get fed back. The other thing we had an issue that we needed EPI-USE for is that we couldn't do a full refresh. There were certain datasets that we had to maintain because they were specific to the end-to-end test environments. So one of the key things was to have a process that was as automated as possible, and where we had the least amount of post-processing work to get the environment back and running. We've started to implement the solution, with EPI-USE products. We have actually installed Data Sync Manager, with Client Sync, Object Sync, System Builder (the whole of the Data Sync Manager suite), into our EE platform. The solution we've put in is basically to ensure that our testing platform has accurate timely data, which we can test with when we're delivering large projects and programs into the live environment. So that helps us to increase the level of confidence in terms of what we're delivering. Our aim was to reduce the footprint, the size of the database, make sure the quality of the data is accurate, from the Production systems. And also, we've put the data scrambling facility in there as well, which again works really, really well. It used to take about a month to take a copy of the Production data and then bring all that data up to date, to help us do the testing in that environment. Now, we've reduced that down to about seventy two hours... So a fantastic achievement.