What advice do you have for others considering Oracle Data Quality?

My company is a partner of Oracle and also a system integrator and consultant for Oracle Data Quality. Oracle Data Quality used to be on-premises, but in 2012, it started to have a cloud version, so nowadays, it's deployed on the cloud. It's part of an Oracle data warehouse, Oracle Data Lake, or Oracle Data Lakehouse, and it's not an independent service on the cloud, but it's part of a larger data management platform service. You don't need additional staff to do the maintenance for Oracle Data Quality. If you have someone in charge of the data platform, analytics, cloud service, or any ETVL purpose, that same person can do the maintenance as well. In terms of development and implementation, anyone experienced in Oracle Data Lakehouse or similar can do it, but if you have a large project, then the different roles could be broken down and assigned to more than one person. From a compliance point of view, you don't need a lot of people for Oracle Data Quality. You can run the solution, implement it, and even provide support for it with a minimal number of people. My advice to anyone planning to implement Oracle Data Quality is to look at the governance and compliance needs first. Before making a decision, you should also look into the features of the solution and evaluate whether those are in-built or if you may have to do a workaround. Oracle Data Quality covers a lot of areas, and I would recommend it, but it's always better to crosscheck first with the compliance and regulation needs of your environment. I would rate Oracle Data Quality nine out of ten because I believe that any product always has room for improvement.

Because we need to do a lot of coding with Oracle Data Quality, we are actually looking into transitioning to a CRM. We like having new ways to interact with the application system, such as to click and drag and to build a program of the flow process. Instead of coding, we would be able to actually build in processes and interact more with the system from the front end. However, I think Oracle Data Quality is definitely worth giving a try. It's a good product. It will help keep your data in line with other systems. So, I would rate it at eight on a scale from one to ten.

We primarily work with the on-premises version, although we do have one project that uses the cloud-based deployment. The cloud version is a recent offering from Oracle. My advice to anybody who is implementing this solution is to understand and define the business needs properly. All of the requirements have to be properly defined. This will allow you to take advantage of the best benefits of Oracle Data Quality. It is important that you don't keep changing the requirements during implementation because it can become very messy. There can be a lot of issues that come from this. Creating the right roadmap for the various types of data is very important. We have not had any major challenges in working with this product. Nonetheless, no product is perfect and there is always an improvement that is needed. I would rate this solution a nine out of ten.