DATPROF Reviews

We had a Broadcom solution. We had an exit strategy for all the tools of this provider. The contracts were supposed to end. DATPROF is more open with respect to outside environments. Of course, it's not open-source technology, but there are provisions to do so, whereas, with earlier tools, that wasn't the case. Another good part of DATPROF is that because they have already been in the market and working with customers for a long time, they know the ins and outs of how the market in the Netherlands works. That was visible when we were performing use cases where the generation of test data was required. Everything that we could possibly think of is already covered by the tool. The inclusiveness or the wholesomeness of the tool is very good. DATPROF's UI is many years ahead of earlier tools. Broadcom's customer support was not up to our requirements. With DATPROF, even though we are just in the sales phase, I already see tremendous improvement. With the earlier tool, they were not able to provide the solutions that we wanted, whereas with DATPROF, Gerard, and Michael are just a call away, and they are willing to extend themselves to provide us with the right support.

The most valuable feature is that it's easy to use. We were using it for Microsoft Dynamics Navision and at a later point in time we had to use it for JD Edwards but we didn't have to go to any other solution. We were able to quickly port a JD Edwards application into the DATPROF solution and we were able to scramble the data in that application. It's a single tool that helps us to do that across applications. And the masking templates are reusable. Microsoft Dynamics Navision has been implemented in at least 19 different operating companies, within our company. It goes into each of the tenants and then it runs it. Without this feature, we would be spending quite a lot of time customizing it individually at each location. The first time you set it up, it takes a lot of time. But if we have one template that can be reused, it becomes fairly simple for us to quickly adapt it. As we speak, we are doing a scrambling setup for one of our large applications. It doesn't take much time. Once you configure it, it becomes a routine. You just press the button and it takes care of it. There is an integration with a product called EPI-USE Labs Data Secure. To integrate these two, we have another product called Symphony, which orchestrates the data masking between SAP and non-SAP applications. SAP masks the data and then Symphony picks it up. Symphony triggers the masking in EPI-USE Labs Data Secure and it takes the masked data reference and passes it onto DATPROF. DATPROF picks up the baton and runs the scrambling using the same ruleset. I have not seen any other solution that makes it easier for scrambling between SAP and non-SAP applications. This is definitely important. Our testers would go crazy if the data in our SAP application and our non-SAP applications looked different.

The data scrambling, the masking, is the most valuable feature. That is how we protect our personal and sensitive information. That is very important for Heineken, given that we work in global scenarios with a lot of personal information and business-sensitive information. This feature is particularly helpful. It is a very intelligent solution when it comes to identifying the dependencies and connections and it is easily scalable. It allows a type of self-service where we are not dependent on the supplier to do the work. Our team members can do things themselves. It is also extremely important that DATPROF's masking for non-SAP databases also integrates with SAP TDM, out-of-the-box. We have operations in more than 100 countries and a majority of those operations use SAP applications. But some of our very important regions, such as the Americas and Asia-Pacific, are using Microsoft Dynamics NAV and Oracle as their core ERPs. That means we have some customers who are in both SAP and non-SAP. When we do scrambling for different applications, it is extremely important that DATPROF and the SAP applications talk to each other and synchronize. Otherwise, for example, if the name Mano is changed to Frank in an SAP system, but the same Mano is changed to Albert in a non-SAP system, that means Mano has two names in two different systems. That means that identity is lost, from a name perspective. It is also quite efficient, as we are doing data refreshes regularly.