What is our primary use case?
We normally use ACL Analytics to automate what we call control testing across different business areas. We have several use cases for procurement which covers accounts payable. We are looking at payroll, employees sharing bank accounts or sharing last names, and all those different HR tests. We have a whole suite of approximately 56 bots testing for six controls. We use it for various business units and we have quite a lot of solutions.
With ACL Analytics alone it is a bit difficult, so we integrated it with a robots application that sits on the cloud. It helps us to control data extraction via our service accounts and automate all that process. In that way, we are able to run a task, and once it is completed, it deletes the data we have extracted from source, only keeping the exceptions that we have.
With ACL Analytics, you have an extension of writing scripts or commands, and what you can do with that is extend it to what they call the HighBond or Diligent robots. That Diligent bot uses Python. Now you are able to create a workflow based on what the result has been on ACL Analytics. For instance, when we have identified a user or a record that is a ghost employee, we need to send that record to business owners. The HighBond or the Diligent cloud bot kicks off the workflow where it triggers an automated notification to the business owner. Then the business owner can provide evidence on that record, and that record feeds back again onto HighBond, which has a storage area also for reporting. That information is stored back into our dataset, and then we are able to analyze it further.
What is most valuable?
The key feature of ACL Analytics is integration, which allows for vast amounts of data sources you can connect to. The tool itself allows you to integrate it into your audit work in terms of taking exceptions that you receive from your analytics. It provides integration into your GRC platform and into your audit working files, and then one key thing is the vast amounts of connectors.
We have seen a return on investment as we have mostly reduced working hours for the audit engagements. If an auditor was normally budgeted to take 600 hours, we have implemented a solution to take those audit hours down to 200 hours. We are mostly taking those metrics.
What needs improvement?
We have an issue with the hard coding of passwords in ACL Analytics. You do not have an interface where you can enter a password and then it can be encrypted when you enter it. Every time you enter a password, it gets exposed under the script, so that is one of the key flaws.
I would definitely want the scalability to be improved in the next releases. The flexibility of getting or sharing suggestions regarding new features could be enhanced.
They can optimize the pricing.
For how long have I used the solution?
I have been working with ACL Analytics for more than 5 years.
What was my experience with deployment of the solution?
Deploying ACL Analytics does not take long; it takes a maximum of a day.
Firstly, you need to get your architecture approval in terms of security regarding what the tool can do and all its different functionalities, including the security flow about sensitive sharing of passwords. Once we have got that approval from architecture, we test the application and run it on the Windows machine as the vendor has specified. To install, we start on the UA environment. To see if it is able to install, we spin up a UA environment and run the installer on our on-prem environment. Then, we check if you can log on into this application since it connects to the internet, ensuring your server can communicate using port 443 or outbound only. That is what has been configured, so you need to test that connectivity to the internet. Once you have done that, your on-prem application will be able to connect or communicate with the internet. That is the testing we do for the desktop application and once we have that, we migrate it onto all the other users across the organization.
What do I think about the stability of the solution?
I would rate how stable this solution is as a 10.
There are minimal downtimes in terms of running analytics. If it is ever down, you also have an option to do a secondary node in case one agent goes down, the other one is able to function. It just depends on the configuration you have done, but in my experience, you should never have any issues in terms of the application itself and its performance, although because of its time-based system, it is probably because our storage we need to acquire more when we are running analytics.
What do I think about the scalability of the solution?
I would rate how scalable ACL Analytics is as a 5. It is a vendor application, and you do not have much power in terms of what we can adjust.
How are customer service and support?
I would rate the technical support for ACL Analytics as a 7.
This rating is due to slow response times; it would take more than 5 days to respond.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Before using ACL Analytics, we used SQL.
We decided to switch from SQL mainly because of connectors; SQL only connects to SQL databases, whereas ACL Analytics connects to multiple databases.
How was the initial setup?
I would rate my experience with the initial setup of ACL Analytics as a 10. Just one person is needed for the deployment.
What about the implementation team?
Currently, three people are needed for the maintenance of this solution.
What was our ROI?
We have seen a return on investment as we have mostly reduced working hours for the audit engagements. If an auditor was normally budgeted to take 600 hours, we have implemented a solution to take those audit hours down to 200 hours. We are mostly taking those metrics.
What's my experience with pricing, setup cost, and licensing?
I would rate the pricing of ACL Analytics as a 10.
Which other solutions did I evaluate?
Before choosing ACL Analytics specifically, we evaluated other options such as IDEA Analytics and Arbutus software.
We chose ACL Analytics over the other options because this one is server-based. With IDEA or Arbutus, it is desktop mode only.
What other advice do I have?
I am a customer of this solution. It depends on new joiners and leavers in the organization. However, based on our contract, we are licensed to have only those 300 licenses, so we maintain them based on the movers and leavers process. My overall rating for ACL Analytics is 8 out of 10.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?