You just bought Auditor (great decision by the way) and you want to know how much time you are going to spend getting it implemented. Since Auditor is such a valuable tool, most people want to get it up and running right away! It helps with fraud prevention, but it can be used for so much more than that. Auditor assists in verifying user performance by calculating how many transactions a user enters and if they do it correctly, procedural verification to guarantee the correct fields are entered and used properly, and it also helps with troubleshooting anomalies occurring in your system.
But enough of what it can do for you, let’s talk about getting it installed and implemented. Don’t worry, installing Auditor is simple and easy. Because Audit information is stored at the system level, this allows the first install you run to create the tables and stored procedures–this will take a little longer than the other installs. Remaining installs will take less time as you’re only installing the code on those machines.
On the first machine, run the Auditor.exe. It works best to right-click and choose ‘Run as Administrator’ when running the Auditor.exe. When you launch Microsoft Dynamics GP after that, you will be prompted to include new code. The Auditor install wizard will run, and this is where the tables and stored procedures are added to the system database. On the remaining machines, you will still run the Auditor.exe and include new code, but the wizard will not run as the tables and procedures are already there. You will want to install Auditor on any machines where you want audits to be captured.
After you have installed Auditor, we highly recommend you sit down with the necessary people and plan out what it is you want to audit. This is actually the biggest part of the implementation and where you could possibly spend the most time. It is important to determine what you need or want to audit as you would not want to audit everything.
Once you have determined what you want to audit, it’s time to begin setting up Auditor. The basic set ups, not including the audits themselves, will depend on what you want to change based on the defaults. When it comes to the audits, this will vary depending on how many audits you want to set up and what you plan to capture.
When your audit library is in place, you will want to do some testing to make sure the needed information is being captured. When you are happy with the results, it is best to export those audits and save them should you ever need to restore your audits.
Here are the estimated times:
Install: 5-10 minutes for the first machine, 3-5 minutes each machine after.
Planning: 1-4 hours to determine what type of audits you want.
Implementing: Set up 2-4 hours and 10-45 minutes for each audit.
Testing: 1 hour of testing
I include time for testing because it is important to always test a new product to make sure it is working as you expect. If you do have any questions or need assistance, you can always contact our support team at firstname.lastname@example.org.
You are ready to install and implement Auditor, but if you are not comfortable implementing or just don’t have time, Rockton Software offers an implementation and training services.