AuditBoard is a cloud-based audit management software solution from the company of the same name in Cerritos.
N/A
MS SharePoint / SQL
Score 8.2 out of 10
N/A
MS SharePoint / SQL refers to Microsoft Sharepoint, a web-based collaborative platform, being used in tandem with Microsoft SQL Server to provide business intelligence analytics and reporting. They can provide BI content such as data connections, reports, scorecards, dashboards, and more.
Auditboard is especially useful for SOX control testing. It is very convenient having all our information on a single platform. It is easy to communicate PBC requests to clients, store control testing working papers for review, communicate deficiencies and build dashboards to provide visual statistics. Situations where it might not be useful are for organizations that are smaller in size where the templates don't fit well with their internal audit/controls program. There is a significant amount of testing required before using the platform, and adapting working papers to fit in well with AuditBoard
As I mentioned in my previous answers, MS SharePoint is very useful as a shared drive for the organization and is very easy to manage. It also helps us import data from SharePoint directly into PowerBI for creating reports. According to my understanding, only share link features should be improved.
We used to perform our Risk Control Analysis (RCA) for each audit's planning in an Excel spreadsheet. Once we purchased the Risk Oversight module, AuditBoard helped us convert the RCA to a system function rather than a spreadsheet. At first, we lost some of the functionality the spreadsheet provided, but AuditBoard did continue to help us build and work towards a solution more similar to what we previously had. Though happy with it, it's still not perfect. As one example, I'd like to be able to link actual Ops Audit work steps that cover the risk and controls being outlined in the RCA, rather than just adding a comment to state which steps cover them. More of a preference, I suppose.
I also had demoed their beta Resources and Scheduling module, but it didn't have enough functionality at the time to work for how we put the quarterly Internal Audit schedule together (using Excel). One thing I recall was that you couldn't pull in SOX controls or non-chargeable work (such as education or administration) to auditor's schedules; it was meant to schedule the Ops Audits only. It is possible they have already fixed or improved this; I just haven't seen the updated version.
This was a long-term buy-in from a corporate perspective, to remain in the SharePoint space. Migration is certainly possible, which is good for planning and having options further out. At this point, the only planned migration is to eventually move the architecture up to SharePoint/SQL 2013. At that point, we will be able to leverage some greater efficiencies, some enhanced content design and management features, and some more current social features. It is well worth a full consideration in any shop looking at a new implementation of or migration to SharePoint (although you will probably be considering 2013 versions or beyond in those discussions), but the platform should be a strong competitor to any alternatives. Realizing the capability of a fully-branded and customized website was not part of the original choice for the architecture at Lincoln, but seeing it implemented and functioning now with this capacity far beyond original expectations has certainly cemented plans to continue using it.
As stated in numerous slides before, asking the same question, SharePoint is the ideal software when working in a fast-paced, team-oriented environment. It is very easy to share large files (PDFs, documents, blueprints) and collaborate with team members inside and outside of our base office.
I've only had to call in to support on one occasion but they were able to work though our issue and find a solution that did fully resolve the issue in a timely manner. I can't always say the same about support from other companies so it was a refreshing change to have support that did help.
I remember there were a lot of sync issues when I used the internally developed software, but that's probably because a few people were working on the same project at the same time. I have not come across this issue in AuditBoard
At the time of the two large projects, SharePoint was the enterprise solution so we were required to use that. We have since lobbied the enterprise teams to review and consider Atlassian Confluence and were successful. Confluence is cheaper than Sharepoint which is why we wanted to bring that in. The enterprise has now made Confluence an enterprise solution as an alternative to SharePoint. After using both I think SharePoint has many more add-ins than Confluence. It has much more customization ability than Confluence. SharePoint is not good for mobile readiness. Confluence is so there is a difference that might lead you to Confluence over SharePoint. I would also say that SharePoint is very document-centric and that Confluence has better KM than SharePoint does. even with the use of SQL Server. We were told that we could not use Google Drive even though it had features we liked.
Hard to quantify. It was cheaper than the tool we had and we were able to get rid of standalone tool for surveys. overall, just better user experience for all.